Transactions are non-trivial.
If you try to implement them yourself from scratch, it’s hard. If you try to implement them on a database that doesn’t support it, you are going to run into a lot of complexities.
If you operate on the assumption that your database has them, but in reality it doesn’t meet the standard, you could be losing data without even knowing it.
With the expansion of IoT data and Time-Series modeling, there is a critical need for a database to offer ACID data consistency without sacrificing your performance, especially as your data scales exponentially.
What exactly makes a Document Database fully transactional? Do MongoDB and RavenDB pass the smell test or do they endanger your data?
In this webinar, Microsoft MVP Oren Eini discusses what a database must prove to be worthy of the coveted “fully-transactional” badge of honor.
He will discuss the challenges presented in the Jepsen article of May 15 and explain how each database answers them.
You will discover:
- What is required of you to enable ACID for each database
- How to maintain your performance while keeping ACID
- How to reduce the complexity of ACID at scale
- Which database offers valid snapshot isolation as part of their ACID promises
- The wealth of knowledge and efficiencies a NoSQL Document Database can accumulate over a decade of keeping ACID