align-toparrow-leftarrow-rightbackbellblockcalendarcamerachatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-crosscrosseditfacebookglobegoogleimagesinstagramlocation-pinmagnifying-glassmailmoremuplabelShape 3 + Rectangle 1outlookpersonplusImported LayersImported LayersImported Layersshieldstartwitteryahoo

Understanding Eventual Consistency and Riak

The success of applications and businesses on the Internet is often measured in converting visitors into customers, retaining user attentions and providing rich experiences, even to mobile devices.  All of these things require responsiveness -- low latency and constant availability.

Riak [3] is a networked key-value database that enables applications to be highly-available and keep latencies low, but requires the developer to grasp eventual consistency.

Sean [1] will discuss why this tradeoff to eventual consistency is necessary (including reviewing the CAP theorem), how Riak implements eventual consistency, and how developers can harness Riak to tackle hard availability problems.



Join or login to comment.

44 went

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy