Wednesday, February 21, 2018

Apache Cassandra vs. Apache Ignite: Strong Consistency and Transactions

DZone Database Zone
Apache Cassandra vs. Apache Ignite: Strong Consistency and Transactions
Apache Cassandra vs. Apache Ignite: Strong Consistency and Transactions

NoSQL databases such as Apache Cassandra are the best-known examples of eventually consistent systems. A contract of such systems is simple: if an application triggers a data change on one machine, then the update will be propagated to all the replicas at some point in time — in other words, eventually.

Until the change is fully replicated, the system as a whole will stay in an inconsistent state. And who knows where the application will end up if it tries to read the changed value from an out-of-sync replica — or even worse, update the value concurrently?

No comments:

Fun With SQL: Functions in Postgres

DZone Database Zone Fun With SQL: Functions in Postgres In our previous  Fun with SQL  post on the  Citus Data  blog, we covered w...