MongoDB 4.0, scheduled for release in Summer 2018*, will add support for multi-document transactions. This will make MongoDB the only database to combine the ACID guarantees of traditional relational databases, the speed, flexibility, and power of the document model, with the intelligent distributed systems design to scale-out and place data where you need it.
Through snapshot isolation, transactions will provide a globally consistent view of data, and enforce all-or-nothing execution to maintain data integrity. Transactions in MongoDB will feel just like transactions developers are familiar with from relational databases, and will be easy to add to any application that needs them. The changes to MongoDB that enable multi-document transactions will not impact performance for workloads that do not require them.
The addition of multi-document transactions will make it easier than ever for developers to address a complete range of use-cases with MongoDB, while for many, simply knowing that they are available will provide critical peace of mind. In MongoDB 4.0 transactions will work across a single replica set, and MongoDB 4.2 will support transactions across a sharded deployment.
In this white paper, we will explore:
- Why MongoDB is adding multi-document ACID transactions
- Their design goals and implementation
- The engineering investments made over the past 3+ years to lay the foundations for them
*Safe Harbour Statement:
The development, release, and timing of any features or functionality described for our products remains at our sole discretion. This information is merely intended to outline our general product direction and it should not be relied on in making a purchasing decision nor is this a commitment, promise or legal obligation to deliver any material, code, or functionality.