If you’re running an operational and transactional system, then you need a database with all of the ACID properties (Atomicity, Consistency, Isolation, and Durability). These properties ensure that your enterprise-grade system never encounters issues like data corruption, stale reads, and inconsistent data. When it comes to mission-critical applications, ACID properties are not a “nice-to-have,” they are an absolute requirement for transactional consistency.

ACID compliance is a standard in relational databases, but MarkLogic is unique among almost all NoSQL databases because we support transactions that are 100% ACID compliant, whereas others have relaxed or even non-existent standards. MarkLogic’s ACID properties also apply to multi-document, multi-statement, and XA transactions (transactions between clusters), providing the unique reliability to run large-scale, operational systems for mission-critical use cases.

Learn More

How MarkLogic Supports ACID Transactions

Mike Wooldridge deep dives into how MarkLogic is ACID compliance and discusses some key MarkLogic features that support ACID properties.

I is for Isolation, That’s Good Enough for Me!

David Gorbet discusses transaction isolation, a.k.a. the I in ACID, and the multiple levels of isolation. Understand how MarkLogic provides repeatable read isolation by default.

How is MarkLogic different from MongoDB?

Tamas Piros reviews significant technical differences between the databases and shows how these differences can impact business-level decisions.

This website uses cookies.

By continuing to use this website you are giving consent to cookies being used in accordance with the MarkLogic Privacy Statement.