Transactions and consistency
When changes are final: one request is one transaction, commit before the response, and where atomicity ends.
Topics in this subject area
- 1.One request, one transaction
Everything in a request succeeds or nothing does. This page explains when a commit and when a rollback happens, and that there is no bracket spanning two requests.
- 2.Create and read back: STRICT or LENIENT
After a create, CDMS reads the object back for the response. What happens when reading back fails is decided by the CreateReadMode.
- 3.No atomicity across two databases
A change that touches the system DB and a tenant DB is not atomic. This page explains when that happens and what it means.
- 4.Files and transaction
File contents are only prepared while the request runs and take effect after the commit. If the request fails, the file storage stays as it was.
- 5.May the client retry?
Which operations can be repeated safely, and for which a repetition creates a second object.