arangodb

History

Simran Brucherseifer e4eeb57e30 Docs: Use standard Markdown notation for headlines and disable MarkdownPP		2016-12-06 02:41:58 +01:00
..
Durability.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00
Limitations.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00
LockingAndIsolation.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00
Passing.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00
README.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00
TransactionInvocation.mdpp	Docs: Use standard Markdown notation for headlines and disable MarkdownPP	2016-12-06 02:41:58 +01:00

README.mdpp

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.