3 ms·

Sites similar to twitter are worried about Read/Writes and up time rather than concurrency and locking mechanisms. All flavors of NOSQL databases are best suite

Sites similar to twitter are worried about Read/Writes and up time rather than concurrency and locking mechanisms. All flavors of NOSQL databases are best suited for this. Sites like amazon.com, or any transaction processing site can't think of using NOSQL. tl:dr; NOSQL is good until transaction processing & concurrency comes in to picture.

andrewtj 17y ago
Scalaris (http://code.google.com/p/scalaris/ http://code.google.com/p/scalaris/) is consistent and has transactions. As an aside, three sentences doesn't really warrant a "tl;dr".
- z8000 17y ago
  Not being snarky here but how can anyone seriously consider Scalaris for any data that's even remotely important? http://code.google.com/p/scalaris/wiki/FAQ#Is_the_store_persisted_on_disk http://code.google.com/p/scalaris/wiki/FAQ#Is_the_store_pers...?
  - andrewtj 17y ago
    It certainly limits it from being useful if you don't have dollars to throw at high-end infrastructure, but it's not quite as terrible as it sounds. Effectively all it means is that you can't cold start it. How big a problem this is depends like anything else on the application in question.
    - z8000 17y ago
      As I write this comment I just know that in 5 years I will look at it and chuckle at myself but... it boggles my mind to consider a pure-RAM system that relies on at least one copy of the dataset being available forever in some system's "memory grid". http://highscalability.com/are-cloud-based-memory-architectures-next-big-thing http://highscalability.com/are-cloud-based-memory-architectu...
rbranson 17y ago
Amazon pioneered Dynamo, a NoSQL-style scalable distributed key-value store, for building many of their site's internal services upon. It's backed by BDB and can be tuned to guarantee disk writes across multiple nodes if needed. See the paper below. http://www.allthingsdistributed.com/2007/10/amazons_dynamo.html http://www.allthingsdistributed.com/2007/10/amazons_dynamo.h...
JulianMorrison 17y ago
MongoDB does implicit transactions around single queries/commands on single documents, that can be complex enough to be used to create always-recoverable or always-resumable protocols.

andrewtj 17y ago

Scalaris (http://code.google.com/p/scalaris/ http://code.google.com/p/scalaris/) is consistent and has transactions. As an aside, three sentences doesn't really warrant a "tl;dr".

z8000 17y ago
Not being snarky here but how can anyone seriously consider Scalaris for any data that's even remotely important? http://code.google.com/p/scalaris/wiki/FAQ#Is_the_store_persisted_on_disk http://code.google.com/p/scalaris/wiki/FAQ#Is_the_store_pers...?
- andrewtj 17y ago
  It certainly limits it from being useful if you don't have dollars to throw at high-end infrastructure, but it's not quite as terrible as it sounds. Effectively all it means is that you can't cold start it. How big a problem this is depends like anything else on the application in question.
  - z8000 17y ago
    As I write this comment I just know that in 5 years I will look at it and chuckle at myself but... it boggles my mind to consider a pure-RAM system that relies on at least one copy of the dataset being available forever in some system's "memory grid". http://highscalability.com/are-cloud-based-memory-architectures-next-big-thing http://highscalability.com/are-cloud-based-memory-architectu...

rbranson 17y ago

Amazon pioneered Dynamo, a NoSQL-style scalable distributed key-value store, for building many of their site's internal services upon. It's backed by BDB and can be tuned to guarantee disk writes across multiple nodes if needed. See the paper below. http://www.allthingsdistributed.com/2007/10/amazons_dynamo.html http://www.allthingsdistributed.com/2007/10/amazons_dynamo.h...

JulianMorrison 17y ago

MongoDB does implicit transactions around single queries/commands on single documents, that can be complex enough to be used to create always-recoverable or always-resumable protocols.