arangodb

History

Simran Brucherseifer 098564f20c Clarify the transaction API's sub-attributes of collections parameter		2016-11-18 01:39:45 +01:00
..
Durability.mdpp	…
Limitations.mdpp	Docs: Limitations in cluster mode	2016-08-24 13:38:47 +02:00
LockingAndIsolation.mdpp	Clarify the transaction API's sub-attributes of collections parameter	2016-11-18 01:39:45 +01:00
Passing.mdpp	Replace more require('internal') by require('@arangodb') where possible	2016-07-27 14:44:17 +02:00
README.mdpp	…
TransactionInvocation.mdpp	replaced require("internal").db by require("@arangodb").db	2016-07-22 16:22:23 +02:00

README.mdpp

!CHAPTER Transactions

Starting with version 1.3, ArangoDB provides support for user-definable 
transactions. 

Transactions in ArangoDB are atomic, consistent, isolated, and durable (*ACID*).

These *ACID* properties provide the following guarantees:

* The *atomicity* principle makes transactions either complete in their
  entirety or have no effect at all.
* The *consistency* principle ensures that no constraints or other invariants
  will be violated during or after any transaction.
* The *isolation* property will hide the modifications of a transaction from
  other transactions until the transaction commits. 
* Finally, the *durability* proposition makes sure that operations from 
  transactions that have committed will be made persistent. The amount of
  transaction durability is configurable in ArangoDB, as is the durability
  on collection level.