Press "Enter" to skip to content

Breaking Open Apache Geode: How It Works and Why



What sparkly facets are on the inside of Apache Geode? How does it work and why is it designed this way?

This session will break down the details of how Apache Geode stores data and maintains consistency. We’ll cover:

– data partitioning and low-latency data access
– redundancy, rebalancing, and member failures

Throughout the talk, we’ll focus on the design considerations behind the choices made by Apache Geode. If you’re interested in what goes into the design of a highly available, low-latency, distributed system, this talk is for you!

Learn more: https://pv.tl/2MVTNni

Speaker: Dan Smith, Principal Software Engineer, Pivotal
Filmed at SpringOne Platform 2019
Slides: https://www.slideshare.net/Pivotal/breaking-open-apache-geode-how-it-works-and-why

1
Leave a Reply

avatar
1 Comment threads
0 Thread replies
0 Followers
 
Most reacted comment
Hottest comment thread
0 Comment authors
Tirthankar Mitra Recent comment authors
  Subscribe  
newest oldest most voted
Notify of
Tirthankar Mitra
Guest
Tirthankar Mitra

I have a question on the read going to any nodes, while writes are locked and kind of done serially for a particular bucket. If reads get an arbitrary copy it might be a problem in some cases. Consider that I am storing balance of an account so without checking the correct balance we could not make a transaction. In short is there a way to put lock on reads as well same as write?