Differences between “NoSQL” databases: Cassandra vs MongoDB vs CouchDB vs Redis vs Riak vs HBase vs Membase vs Neo4j

Aa comparison ofCassandra,Mongodb,CouchDB,Redis,Riak,Membase,Neo4j and HBase. It shows general information about the features of each NoSQL database systems to make a decision which one to use.

The original post is here. Also read the discusson on HackerNews.

CouchDB

• Written in: Erlang
• Main point: DB consistency, ease of use
• License: Apache
• Protocol: HTTP/REST
• Bi-directional (!) replication,
• continuous or ad-hoc,
• with conflict detection,
• thus, master-master replication. (!)
• MVCC – write operations do not block reads
• Previous versions of documents are available
• Crash-only (reliable) design
• Needs compacting from time to time
• Views: embedded map/reduce
• Formatting views: lists & shows
• Server-side document validation possible
• Authentication possible
• Real-time updates via _changes (!)
• Attachment handling
• thus, CouchApps (standalone js apps)
• jQuery library included

Best used: For accumulating, occasionally changing data, on which pre-defined queries are to be run. Places where versioning is important.

For example: CRM, CMS systems. Master-master replication is an especially interesting feature, allowing easy multi-site deployments.

Redis

• Written in: C/C++
• Main point: Blazing fast
• License: BSD
• Protocol: Telnet-like
• Disk-backed in-memory database,
• but since 2.0, it can swap to disk. (Going away after 2.4!)
• Master-slave replication
• Simple values or hash tables by keys,
• but complex operations like ZREVRANGEBYSCORE.
• INCR & co (good for rate limiting or statistics)
• Has sets (also union/diff/inter)
• Has lists (also a queue; blocking pop)
• Has hashes (objects of multiple fields)
• Sorted sets (high score table, good for range queries)
• Redis has transactions (!)
• Values can be set to expire (as in a cache)
• Pub/Sub lets one implement messaging (!)

Best used: For rapidly changing data with a foreseeable database size (should fit mostly in memory).

For example: Stock prices. Analytics. Real-time data collection. Real-time communication.

MongoDB

• Written in: C++
• Main point: Retains some friendly properties of SQL. (Query, index)
• License: AGPL (Drivers: Apache)
• Protocol: Custom, binary (BSON)
• Master/slave replication (auto failover with replica sets)
• Sharding built-in
• Queries are javascript expressions
• Run arbitrary javascript functions server-side
• Better update-in-place than CouchDB
• Uses memory mapped files for data storage
• Performance over features
• Journaling (with –journal) is best turned on
• On 32bit systems, limited to ~2.5Gb
• An empty database takes up 192Mb
• GridFS to store big data + metadata (not actually an FS)

Best used: If you need dynamic queries. If you prefer to define indexes, not map/reduce functions. If you need good performance on a big DB. If you wanted CouchDB, but your data changes too much, filling up disks.

For example: For most things that you would do with MySQL or PostgreSQL, but having predefined columns really holds you back.

Riak

• Written in: Erlang & C, some Javascript
• Main point: Fault tolerance
• License: Apache
• Protocol: HTTP/REST or custom binary
• Tunable trade-offs for distribution and replication (N, R, W)
• Pre- and post-commit hooks in JavaScript or Erlang, for validation and security.
• Map/reduce in JavaScript or Erlang
• Links & link walking: use it as a graph database
• Large object support (Luwak)
• Comes in “open source” and “enterprise” editions
• Full-text search, indexing, querying with Riak Search server (beta)
• Masterless multi-site replication replication and SNMP monitoring are commercially licensed

Best used: If you want something Cassandra-like (Dynamo-like), but no way you’re gonna deal with the bloat and complexity. If you need very good single-site scalability, availability and fault-tolerance, but you’re ready to pay for multi-site replication.

For example: Point-of-sales data collection. Factory control systems. Places where even seconds of downtime hurt. Could be used as a well-update-able web server.

Membase

• Written in: Erlang & C
• Main point: Memcache compatible, but with persistence and clustering
• License: Apache 2.0
• Protocol: memcached plus extensions
• Very fast (200k+/sec) access of data by key
• Persistence to disk
• All nodes are identical (master-master replication)
• Provides memcached-style in-memory caching buckets, too
• Write de-duplication to reduce IO
• Very nice cluster-management web GUI
• Software upgrades without taking the DB offline
• Connection proxy for connection pooling and multiplexing (Moxi)

Best used: Any application where low-latency data access, high concurrency support and high availability is a requirement.

For example: Low-latency use-cases like ad targeting or highly-concurrent web apps like online gaming (e.g. Zynga).

Neo4j

• Written in: Java
• Main point: Graph database – relationships
• License: GPL, some features AGPL/commercial
• Protocol: HTTP/REST (or embedding in Java)
• Standalone, or embeddable into Java applications
• Both vertices and edges can have metadata
• Nice self-contained web admin
• Advanced path-finding with multiple algorithms
• Indexing of keys and relationships
• Optimized for reads
• Has transactions (in the Java API)
• “Gremlin” graph traversal language
• Scriptable in Groovy
• Online backup, advanced monitoring and High Availability is AGPL/commercial licensed

Best used: For graph-style data. Neo4j is quite different from the others in this sense.

For example: Social relations, public transport links, road maps, network topologies.

Cassandra

• Written in: Java
• Main point: Best of BigTable and Dynamo
• License: Apache
• Protocol: Custom, binary (Thrift)
• Tunable trade-offs for distribution and replication (N, R, W)
• Querying by column, range of keys
• BigTable-like features: columns, column families
• Writes are much faster than reads (!)
• Map/reduce possible with Apache Hadoop
• I admit being a bit biased against it, because of the bloat and complexity it has partly because of Java (configuration, seeing exceptions, etc)

Best used: When you write more than you read (logging). If every component of the system must be in Java. (“No one gets fired for choosing Apache’s stuff.”)

For example: Banking, financial industry (though not necessarily for financial transactions, but these industries are much bigger than that.) Writes are faster than reads, so one natural niche is real time data analysis.

HBase

• Written in: Java
• Main point: Billions of rows X millions of columns
• License: Apache
• Protocol: HTTP/REST (also Thrift)
• Modeled after BigTable
• Map/reduce with Hadoop
• Query predicate push down via server side scan and get filters
• Optimizations for real time queries
• A high performance Thrift gateway
• HTTP supports XML, Protobuf, and binary
• Cascading, hive, and pig source and sink modules
• Jruby-based (JIRB) shell
• No single point of failure
• Rolling restart for configuration changes and minor upgrades
• Random access performance is like MySQL

Best used: If you’re in love with BigTable. 🙂 And when you need random, realtime read/write access to your Big Data.

For example: Facebook Messaging Database (more general example coming soon)