Learn about our cloud-native data integration experience.
Learn about our cloud-native data integration experience.
Learn about our cloud-native data integration experience.
Learn about our cloud-native data integration experience.
Learn about our cloud-native data integration experience.
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.
ABN AMRO needed to respond quickly to changing regulatory requirements. MarkLogic’s multi-model database and associated features such as security and ACID transactions were compelling.
CMS launched HealthCare.gov on MarkLogic within 18 months, achieving over 5,500 transactions per second and enabling over 8 million people to sign up for health insurance in its first year of operation.
A Top Five Investment Bank runs its operational trade store on MarkLogic, processing over 100,000 complex trades each day that typically result in about 32 million live deals in the system at any one time.
Document locks to protect data during updates and keep transactions from conflicting with one another
Timestamps on documents that ensure a query only sees copies of documents that are valid at the time the query is run (also known as Multi-Version Concurrency Control)
Journaling of updates before they are committed to ensure transactions can be replayed in the face of system failures
A commit process to ensure changed data is changed all at once or not at all, even across multiple hosts
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.
Be the first to know! News, product information, and events delivered straight to your inbox.
By continuing to use this website you are giving consent to cookies being used in accordance with the MarkLogic Privacy Statement.