Friday, January 24, 2014

Coding for Eventual Consistency

Jan Lehnardt recently wrote Understanding CouchDB Conflicts, which explains some of the nit and grit behind eventual consistency in CouchDB and Cloudant, but underlying Jan’s article is the question, "How does eventual consistency change how I should write applications?"

Whether your database guarantees strong consistency (where every part of a distributed system sees the same data at the same time) or high availability (where all requests receive responses, regardless of system failure) changes what you can expect of it. No distributed database can guarantee both while remaining meaningfully distributed, so it’s important to understand how you build applications given the tradeoff.

So, as a developer, how should you code for eventual consistency?

Read more here

Leave a Reply

All Tech News IN © 2011 & Main Blogger .