Good NoSQL Database (with some SQL still inside)
September 03, 2020

Good NoSQL Database (with some SQL still inside)

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Couchbase

It was initially a cache (caching data aggregated from multiple sources, with various response time and rate limiters), but as usage grew, confidence grew also, we started also using it a database with NoSQL, to query multiple documents based upon more and more complex queries, to fit our needs.
  • Key value access is super fast.
  • NoSQL is particularly useful when you have a SQL background.
  • .Net client works like a charm and is well maintained.
  • With NoSQL, you kind of have a vendor locked in.
  • When something goes wrong, rarely, it's sometimes hard to find the culprit using the statistics.
  • We feel we are missing some features by using the community edition, but we survive.
  • When we have a performance issue, we throw Couchbase at it, and it usually works!
  • Super resilient
  • XDCR works like a charm.
We have the "bare minimum" hardware for high availability: 6 nodes (3 on each datacenter + XDCR) and performance has been amazing, even during that one period (of 6 months), where, by mistake, we started caching 10x more data than before. Also, we added some Elastic APM on top of it and each time we see a NoSQL query taking longer than expected, adding indexes quickly solves the issue.
We are an API gateway to our huge IT Systems (30 systems accessed using the gateway), and Couchbase serves as a cache for all those dependencies. It allows us to serve our client with response times well below what could be achieved without Couchbase.
Primarily for the fast Key Value Store, with a good .Net client. NoSQL made perfect sense when we started having some data on Couchbase and with our SQL background, it was easy. No need for training.
I'm not qualified enough to make a meaningful comparison, but 2 years after, I hear regularly about issues on Mongo from the other teams, especially on the SRE side. On our side, not much to say, except that it works. Ram, CPU, disk behave like expected. Same for bandwidth. Response time stays low. Not much to add.
Couchbase is well suited to a fast distributed Key Value store with a light need of SQL-like language for access. Below 5 minutes response time is usual for KV access, nearly impossible for SQL/HTTP call in our systems. It saves us.

Couchbase Feature Ratings

Performance
9
Availability
9
Concurrency
9
Security
9
Scalability
8
Data model flexibility
10
Deployment model flexibility
10