ACID Transactions

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 “nice to have” — they are an absolute necessity for transactional consistency.

ACID compliance is a standard in relational databases, but MarkLogic is unique among almost all NoSQL databases– 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, providing unique reliability to run large-scale, operational systems for mission-critical use cases.

Here you’ll find some technical resources that help explain ACID Transactions in MarkLogic.

Mike Wooldridge deep dives into how MarkLogic is ACID-compliant while discussing some key features of MarkLogic that support ACID properties.

Read the Blog

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

Read the Blog

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

Read the Blog

Read or download the PDF document that summarizes how MarkLogic satisfies all of the ACID properties by using MVCC.

Go to Resource

This chapter of the Application Developer’s Guide describes the transaction model of MarkLogic Server.

Read the documentation

The MarkLogic CTO, Ken Krupta, explains why your organization needs ACID Transactions, and why it’s especially important for running mission critical applications.

Read the blog

Feature

Learn More

Stay on top of everything Marklogic.

This website uses cookies.