ACID Compliant Transaction


 

Oracle NoSQL Database provides ACID complaint transactions for full Create, Read, Update and Delete (CRUD) operations, with adjustable durability and consistency transactional guarantees.

You can also execute a sequence of operations as a single atomic unit as long as all the records that are going to be operated upon share the same Major Key Path. By atomic unit, we mean all of the operations will execute successfully, or none of them will.

 

For example, suppose you have stored user profile information in your database and you would like to update "birthdate", "image", "phonenumber", "userID", of a particular user as a single atomic transaction (here, for illustration purposes, we delimit the Major Key Path by a forward slash (“/”) and Minor Key Path using a dot (".")).  

 

Smith/Bob.birthdate

Smith/Bob.phonenumber

Smith/Bob.image

Smith/Bob.userID

Smith/Patricia.birthdate

Smith/Patricia.phonenumber

Smith/Patricia.image

Smith/Patricia.userID

 

You can use execute method which provides an efficient and transactional mechanism for executing a sequence of operations associated with keys that share the same Major Key Path.

Consistency Spectrum

 Oracle NoSQL Database provides several different consistency policies. At one end of the spectrum, applications can specify absolute consistency, which guarantees that all reads return the most recently written value for a designated key. At the other end of the spectrum, applications capable of tolerating inconsistent data can specify weak consistency, allowing the database to return a value efficiently even if it is not entirely up to date. In between these two extremes, applications can specify time-based consistency to constrain how old a record might be or version-based consistency to support both atomicity for read-modify-write operations and reads that are at least as recent as the specified version.


Durability Spectrum

Oracle NoSQL Database also provides a range of durability policies that specify what guarantees the system makes after a crash. At one extreme, applications can request that write requests block until the record has been written to stable storage on all copies. At the other extreme, applications can request that write operations return as soon as the system has recorded the existence of the write, even if the data is not persistent anywhere.

KScope 14 RHS Banner

Database Cloud Service Banner