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



membase: All content tagged as membase in NoSQL databases and polyglot persistence

NoSQL Databases: What, Why, and When

Lorenzo Alberton with an overview of the NoSQL landscape:

NoSQL databases get a lot of press coverage, but there seems to be a lot of confusion surrounding them, as in which situations they work better than a Relational Database, and how to choose one over another. This talk will give an overview of the NoSQL landscape and a classification for the different architectural categories, clarifying the base concepts and the terminology, and will provide a comparison of the features, the strengths and the drawbacks of the most popular projects (CouchDB, MongoDB, Riak, Redis, Membase, Neo4j, Cassandra, HBase, Hypertable).

RethinkDB Launches 1.0 Version With Memcached Compatibility Only

Just as I speculated , RethinkDB has finally launched the 1.0 version with Memcached compatibility only. Jason Kincaid (Techcrunch) writes:

RethinkDB has just launched its 1.0 release to the public, and it’s offering a product geared toward NoSQL installations — and it will work on SSDs, traditional drives, and cloud-based services like AWS. The startup has also moved away from MySQL and now fully supports Memcached.

But RethinkDB is not the first product providing a Memcached compatible (disk) persistent storage engine. One year ago Membase was launched promising not only a persistent Memcached compatible solution, but also elastic scalability.

RethinkDB has also published a performance report (PDF) demonstrating RethinkDB speed compared to Membase and MySQL. But if I’m reading those numbers correctly, while RethinkDB leads the majority of query-per-second (QPS) benchmarks, MySQL is consistently showing better latency numbers (which is kind of weird). For a strong durability scenario, the benchmark shows MySQL delivering 2x QPS compared to RethinkDB.

Another interesting aspect of the RethinkDB 1.0 release is the licensing model —which I don’t fully get:

RethinkDB Basic is currently identical in feature-set to RethinkDB Premium and Enterprise. However, the paid versions of RethinkDB include phone and email support, access to all future updates, and volume licensing options.

Or spelled out on the TechCrunch post :

Akhmechet says that the free version will get security updates, but that it won’t necessarily receive new features in the future, whereas the premium version will.

Original title and link: RethinkDB Launches 1.0 Version With Memcached Compatibility Only (NoSQL databases © myNoSQL)

Membase on Amazon EC2 with EBS

The decision was made and we decided to go with a 2 server solution, each server has 16G of memory and 100G of EBS volume attached to it.

Both will have membase latest stable version installed and perform as a cluster in case one falls or anything happens, a fail safe if you will.

In this post, I will walk you though what was done to perform this and how exactly it was done on the amazon cloud.

Wouldn’t it be easier if there would be an always up-to-date official Membase AMI and the corresponding guide (making sure important details about EBS are not left out)?

Original title and link: Membase on Amazon EC2 with EBS (NoSQL databases © myNoSQL)


Powered by Membase: Ad Platform AdAction

Wouter de Bie (systems developer for AdAction):

We needed a system that is simple to use and manage, provides low latency and high throughput, and expands to support our business at any scale. Our future success is tied to our ability to deploy new nodes seamlessly, on demand, with no downtime or time-consuming manual re-balancing. The new infrastructure enables us to deliver on our promise — highly targeted ads served within 100 milliseconds 99.99% of the time. As a result, we are delivering a consistently excellent service for our clients and their end customers.

They also characterize Cassandra as “sluggish in performance, cumbersome to rebalance and required significant downtime for upkeep and expansion”.

Original title and link: Powered by Membase: Ad Platform AdAction (NoSQL databases © myNoSQL)


AOL AdLead Powered by Riak Components

A story of using Riak for its Dynamo-like building blocks:

I made use of riak-kv, riak-search, and riak-core to help distribute my application’s data, state, and processing, respectively. These technologies provided me with a framework I could use instead of trying to build the functionality myself. This allowed me to put the entire application behind a dumb splitter and call it a day. A horizontal scale out is a simple matter of standing up a new node, joining it to the cluster, and adding an entry to the splitter.

The usage of riak-search as a distributed file index is interesting, given there’s also Luwak — but that Riak library is meant for large files.

As the author mentions this is an internal application of AOL Advertising. The public facing AOL Advertising is using Membase and Hadoop.

Original title and link: AOL AdLead Powered by Riak Components (NoSQL databases © myNoSQL)