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.
ACID is an acronym representing four key properties that guarantee your database transactions are reliably processed.
The promise of NoSQL is speed and scale. But, in order to achieve speed and scale, most distributed databases sacrifice transactional consistency. Or, they only maintain transactional consistency using single-document locks. This means that if a transaction involves multiple documents, then you can forget about transactional consistency. That’s like saying your brakes always work… except when you’re on the highway.