ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close
Monday, 27 September 2010
‹ Back

Alternatives to Database Transactions

About:
,

Ashwin Jayaprakash:

[…] there still are many systems where data flows across large applications; where a simpler, resilient and more predictable compensating mechanism is suitable. Simpler it may be, but designing such systems require a lot of foresight and expertise:

  • Optimistic concurrency based on version numbers
  • Atomic compare-and-swap upsert/update operations
  • Polite Spin locks and backoff-retry mechanisms
  • Clear error reporting
  • State capture, repair and consistency checking
  • Operation logging, undo and re-apply
  • Proper documentation and involvement of Developer/Architect

Original title and link: Alternatives to Database Transactions (NoSQL databases © myNoSQL)

via: http://javaforu.blogspot.com/2010/09/txncommit-are-you-sure.html