Thursday, August 7, 2014

How to implement robust and scalable transactions across documents with MongoDB

here are some good reasons why historically databases have provided support for transactions across pieces of data. The typical scenario is that the application needs to modify several independent bits and it would likely get into a bad state if only some of those changes actually made it to the datastore. Hence the concept of the long-revered ACID:

  •  Atomicity: all changes are made, or none 
  • Consistency: data remains in a consistent state 
  • Isolation: other clients cannot see partial changes 
  • Durability: once the transaction is acknowledged back to the client, the data is in a safe spot (typically in a journal on disk)
Read more here

Leave a Reply

All Tech News IN © 2011 & Main Blogger .