Couchbase vs Riak

• Easy to store unstructured data and has great performance
• Managing security is super easy which can be managed across different levels
• UI is pretty simple to use and manage the cluster
• Backup of the data is very easy and the restoration/recovery is fairly easy as well with the in-built tools.
• Easy integration with elasticsearch for replication
• It is fairly easy to scale up or scale down the cluster

Read full review

• Riak is great at handling large volumes of requests. We've seen Riak perform well under large volume while keeping response times quite low.
• Riak is also fast providing consistent sub 10ms reads in both the datacenter and cloud.
• Flexible allowing storage of numerous data types. We heavily leverage this to store various JSON documents in a single bucket.
• We really like the RESTful interface that is provided. Makes the learning curve almost invisible and provides a quick speed to market in using Riak.

Read full review

• Community edition has various limitations, like [the] inability to view/edit documents over a certain threshold or inability to use various types of [optimized] indexes.
• The indexes performance degrades when a certain number of mutations is reached.
• The views creation can be quite slow and impacts the deployment speed for large buckets.

Read full review

• It does not have any native startup scripts in Linux.
• Since it's built on Erlang, its a bit difficult to administer.

Read full review

• N1QL's SQL-like syntax has made bringing new developers up to speed both easy and inexpensive.
• The schema-less approach to data store has increased agility.
• Operating at scale, Couchbase tends to be less expensive than major RDBMS solutions, especially once you implement high availability in RDBMS.

Read full review

• Riak has been a key part of our company's build process for our client's search backend. It is valuable for is in that it provides a reliable way to view the current search index.

Read full review