Does The Documentdb Api Support Acid Transactions?

1.	Does The Documentdb Api Support Acid Transactions?
Answer» Yes, the DocumentDB API supports cross-document transactions expressed as JavaScript-stored PROCEDURES and triggers. Transactions are scoped to a single partition within each collection and executed with ACID semantics as "all or nothing," isolated from other concurrently executing CODE and user requests. If exceptions are thrown through the server-side execution of JavaScript application code, the ENTIRE transaction is rolled back. Yes, the DocumentDB API supports cross-document transactions expressed as JavaScript-stored procedures and triggers. Transactions are scoped to a single partition within each collection and executed with ACID semantics as "all or nothing," isolated from other concurrently executing code and user requests. If exceptions are thrown through the server-side execution of JavaScript application code, the entire transaction is rolled back.

Answer»

Yes, the DocumentDB API supports cross-document transactions expressed as JavaScript-stored PROCEDURES and triggers. Transactions are scoped to a single partition within each collection and executed with ACID semantics as "all or nothing," isolated from other concurrently executing CODE and user requests. If exceptions are thrown through the server-side execution of JavaScript application code, the ENTIRE transaction is rolled back.

Yes, the DocumentDB API supports cross-document transactions expressed as JavaScript-stored procedures and triggers. Transactions are scoped to a single partition within each collection and executed with ACID semantics as "all or nothing," isolated from other concurrently executing code and user requests. If exceptions are thrown through the server-side execution of JavaScript application code, the entire transaction is rolled back.

Discussion

No Comment Found

Related InterviewSolutions

Are There Changes To Pricing?
What Changes Do I Need To Make For My App To Work With Azure Cosmos Db?
What Do I Need To Do To Ensure That My Documentdb Resources Continue To Run On Azure Cosmos Db?
Why Are You Moving To Azure Cosmos Db?
Azure Cosmos Db As A Platform Seems To Have Lot Of Capabilities, Such As Change Feed And Other Functionality. Will These Capabilities Be Added To The Cassandra Api?
Does The Apache Cassandra Api Index All Attributes Of An Entity By Default?
How Does The Cassandra Api Account Handle Failover If A Region Goes Down?
Does Cassandra Api Provide Full Backups?
Can I Use Stable Loader For Data Loading?
Is Composite Partition Key Supported?