Couchbase Products Comparison Table
Here are two ways to determine which of our NoSQL solutions is right for your application. The table below gives you a seriously detailed means for evaluation. And, on a more simplified level:
Couchbase Single Server is a fit if:
-
A single-server solution is enough to support your users and data
-
Advanced querying and indexing is important
-
You demand peer-to-peer sync
Membase Server is a fit if:
-
You have large number of users
-
Multiple servers are necessary to support growing user population and data set
-
Low latency, high throughput are needed for snappy interactive experience
Memcached-mode Membase is a fit if:
-
You're using another primary database technology (like Couchbase) but want to cache some data in memory to get low-latency
-
You want a pathway to Membase
|
Simple |
Membase Server |
Couchbase Single Server |
Membase Server
(memcached mode) |
|
Easy to get, install and use
|
♦ |
♦ |
♦ |
|
Disk persistence |
♦ |
♦ |
|
|
Single node fault tolerance |
♦ |
♦ |
|
|
Apache CouchDB compatible |
|
♦ |
|
|
Memcached API compatible |
♦ |
|
♦ |
|
Lists and sets support |
o |
|
|
|
Enterprise production ready |
♦ |
♦ |
♦ |
|
Developer GUI |
|
♦ |
|
|
Map Reduce support |
|
♦ |
|
|
Flexible views and querying |
|
♦ |
|
|
Secure resource managed multi-tenancy |
♦ |
|
♦ |
|
Seamless upgrade path to Membase |
|
|
♦ |
|
Flexible schema-less data repository |
♦ |
♦ |
♦ |
|
Full-featured REST API and CLI |
♦ |
♦ |
♦ |
|
User management |
♦ |
♦ |
♦ |
|
World-class support |
♦ |
♦ |
♦ |
|
Fast |
Membase Server |
Couchbase Single Server |
Membase Server
(memcached mode) |
|
Durable speed w/o compromising safety
|
♦ |
♦ |
|
|
Managed memcached caching layer |
♦ |
|
♦ |
|
Indexing |
|
♦ |
|
|
Sub-millisecond access latency |
♦ |
|
♦ |
|
Single-node ops/second ranges |
50k-100k |
2k-4k |
50k-100k |
|
High-speed failover |
♦ |
|
|
|
In-memory key indexing |
♦ |
|
♦ |
|
Client-side proxy option |
♦ |
|
|
|
Elastic |
Membase Server |
Couchbase Single Server |
Membase Server
(memcached mode) |
|
Peer-to-peer replication
|
♦ |
♦ |
|
|
Mobile synchronization |
|
♦ |
|
|
Multi-node clusters |
♦ |
|
♦ |
|
Zero downtime topology change |
♦ |
|
|
|
Optional synchronous replication |
♦ |
♦ |
|
|
Configurable number of replicas |
♦ |
♦ |
|
|
Spreads data across clusters |
♦ |
|
♦ |
|
Caching and DB semantics in single cluster |
♦ |
|
|
|
Guaranteed data consistency |
♦ |
|
♦ |
|
Configurable “Tap” interface |
♦ |
|
|
|
Node homogeneity |
♦ |
|
♦ |
♦ = current feature
o = coming soon