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



NoSQL Wants To Be Elastic Caching When It Grows Up… Does It Really?

While I’d probably love having the talent to write such ☞big statements, I’d still prefer to get things right firstly:

Elastic Caching Platforms Are KV Stores On Steroids


NoSQL Wants To Be Elastic Caching When It Grows Up


Say “Yes” To Elastic KV Stores In Your Architecture

I confess that I see this whole NoSQL and Elastic caching discussion quite differently, as right now it looks to me that elastic caching is the one missing features (especially persistence) and not the other way around. So maybe, Mike Gaultieri, the author of the above quotes, meant the opposite: elastic caching will become NoSQL when it grows up.

Update: Jeff Darcy (@Obdurodon) ☞ is at it again with a much more detailed comment than I could come up with.

I’m not saying that IMDGs (nb: in memory data grids) aren’t valuable. They can be a very valuable part of an application’s computation or communication model. When it comes to that same application’s storage model, though, IMDGs are irrelevant and shouldn’t be presented as alternatives to various kinds of storage.