Item: Couchbase Server
Rating: 5
Author: Verified User

Use Cases and Deployment Scope

Couchbase is the noSQL solution we use. It's used for various applications from websites, mobile apps to caching. It's primarily used to support legacy DB technologies and website caching.

Pros and Cons

Reliability: rarely goes down.
Supporting legacy DB applications: Putting Couch in front of slow running applications seems to be a good fit.

SDK: Documentation could be better. Questionable decision making in terms of how things work.
Speed: It's being used for our caching solution, however, nobody probably should do this. Far better platforms that handle caching better.
Community: Can be frustrating trying to solve problems seems the community and gender issues vary depending on the version.
Tuning/troubleshooting tools: Improvement should happen in this area.
Adoption: Small compared to other noSQL solutions.

Return on Investment

Scalability

This is an area where Couchbase does well. Scalability is one of its strengths.

Performance

Once Couchbase is properly tuned and the applications are optimized, the speed and handling volume will be adequate.

Alternatives Considered

MongoDB and Redis

I can't speak to the final decision to choose Couchbase. However, if we had to do it over again I'm unsure if Couchbase would beat out other solutions.

Likelihood to Recommend

I don't see much, if any, advantages Couchbase has compared to Mongo. The N1QL query language is nice but probably not an overwhelming reason to chose Couchbase.

Our experience with Couchbase

Overall Satisfaction with Couchbase