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



Amazon DynamoDB: All content tagged as Amazon DynamoDB in NoSQL databases and polyglot persistence

Amazon’s DynamoDB Shows Hardware as Means to an End... Actually It's All About Predictability

Derrick Harris:

In that sense, DynamoDB is something of a curveball. It lets AWS users leverage the performance of SSDs, only as the underpinning of a new service rather than as a new IaaS feature alone.


Web developers use NoSQL databases more frequently than enterprise developers, and NoSQL requires solid-state performance.

I think Derrick got this mostly wrong this time. Developers do not care about SSDs per se. What good developers care about is performance. And great developers care about predictability of performance.

There are a couple of NoSQL databases that know this very well. To give you just a couple of examples, take a look at this benchmark of Riak and see what is it focusing on. Or check Riak’s Bitcask backend—here’s also a great explanation of the Bitcask paper—which guarantees a single disk seek per read. I assume you guessed the keyword behind both of these: predictability.

Amazon DynamoDB is using SSDs because:

  • it wants to offer predictable low latency
  • it wants to offer predictable throughput
  • it wants to offer single-digit millisecond average service-side responses
  • and it wants to do all these at any scale of dataset sizes and request rates

Hardware is a means to an end. And SSD or not, the aboves are all that matter[1].

  1. There are other dimensions of systems that are as critical as the ones covered (e.g. availability, fault-tolerance, etc.), but these are less related to the SSD vs spinning-disks discussion.  

Original title and link: Amazon’s DynamoDB Shows Hardware as Means to an End… Actually It’s All About Predictability (NoSQL database©myNoSQL)


Introducing Amazon DynamoDB Video

The live broadcast of today’s Amazon DynamoDB announcement went down, so here’s the complete video featuring Werner Vogels (CTO Amazon), Swami Svbasubramanian (GM of DynamoDB), and Don MacAskill (CEO SmugMug)

Cassandra and Amazon DynamoDB Comparison

Maybe a couple of too strong words, but definitely a great comparison of Cassandra and Amazon DynamoDB by Jonathan Ellis (Cassandra chair and founder of DataStax):

As an engineer, it’s nice to see so many of Cassandra’s design decisions imitated by Amazon’s next-gen NoSQL product. I feel like a proud uncle! But in many important ways, Cassandra retains a firm lead in power and flexibility.

Cassandra vs Amazon DynamoDB

Update: this is the updated version of the comparison.

Original title and link: Cassandra and Amazon DynamoDB Comparison (NoSQL database©myNoSQL)


Amazon DynamoDB - a Fast and Scalable NoSQL Database Service Designed for Internet Scale Applications

Werner Vogels:

Today is a very exciting day as we release Amazon DynamoDB, a fast, highly reliable and cost-effective NoSQL database service designed for internet scale applications. DynamoDB is the result of 15 years of learning in the areas of large scale non-relational databases and cloud services.

No words can describe (yet) the magnitude of this announcement.

Original title and link: Amazon DynamoDB - a Fast and Scalable NoSQL Database Service Designed for Internet Scale Applications (NoSQL database©myNoSQL)