Basically we have clusters, Couchbase clusters, databases, and that is how we use Couchbase with XDCR. All the clusters are set up and then we use Couchbase. It is a complex application setup we use with Couchbase. We have replication and multi-node Couchbase setup.
External reviews
External reviews are not included in the AWS star rating for the product.
Cross-data replication and indexing improve data handling while upgrades require more attention
What is our primary use case?
What is most valuable?
The very useful feature of Couchbase is the online addition and deletion of nodes which we use because of XDCR replication. We use this very regularly.
Couchbase has an indexing part that is easy to build. We can create indexes in advance, before we have the data, and then we can stack in the data. This is something we use regularly.
What needs improvement?
The main issue we keep facing from the past couple of years, observing other teams using Couchbase, is that whenever there is an upgrade, we see many issues with compatibility or nodes not interconnecting after the upgrade. The upgrade part should be taken care of very carefully.
We contacted Couchbase support recently when we had a similar issue. They were helping, but it is a critical system and application we have set up. They need to rethink about their upgrade process and improve their validation part after the upgrade.
My team has contacted Couchbase support directly. I think they provide good support, but we prefer a proactive approach rather than reactive because this is not the first time we are facing issues after an upgrade. It has happened two or three times. We need to be very cautious during upgrades, and application teams get worried because of earlier experiences. We need to avoid these situations.
For how long have I used the solution?
Our team has been using Couchbase for a while, but I started using it only in the last year.
What do I think about the stability of the solution?
We encounter compatibility issues with JDK and similar technologies whenever we perform upgrades. We had some issues recently.
How are customer service and support?
We contacted Couchbase support recently when we had an issue. They were helpful, but since we have a critical system and application, they need to rethink their upgrade process and improve their validation after upgrades.
My team has contacted Couchbase support directly. They provide good support, but we prefer a proactive approach rather than reactive because this is not the first time we are facing issues after an upgrade. It has happened multiple times, requiring extra caution during upgrades, which causes worry among application teams due to previous experiences.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I worked with other document databases, MongoDB database and Firestore. Each database has its own advantages and disadvantages. When it comes to the deployment part, MongoDB was much easier to deploy, but there are many differences when comparing features.
Which other solutions did I evaluate?
I worked with other document databases including MongoDB and Firestore. Each database has its own advantages and disadvantages. When it comes to deployment, MongoDB was much easier to deploy, but there are significant feature differences.
I prefer both, but for complex applications requiring minimal downtime, I prefer Couchbase. If there is room for downtime, I would choose MongoDB.
What other advice do I have?
It is a good solution, but as every product needs improvement, this also needs some enhancement. It is a good product. I rate Couchbase seven out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
G2 is recommendable
Scalability – Easily handles growing workloads with horizontal scaling.
High memory and CPU usage, especially at scale.
Very useful for company details
A great NoSql solution company
This makes it easier to support growing applications without significant re-architecting or performance degradation. If you're working on applications that need to handle millions of users or petabytes of data, Couchbase can scale to meet those demands.
Has efficient migration process, but the grouping features need improvement
What is our primary use case?
We manage our telecommunication application using the product.
What is most valuable?
The product's most valuable features are its overall availability and robustness. It is highly available for support and does not impact our operations significantly during failures. It performs very well in terms of speed, particularly for write operations.
What needs improvement?
The platform's grouping features need improvement. Additionally, it supports only a few storage types, which presents challenges, particularly for I/O operations.
For how long have I used the solution?
I have been working on Couchbase for the last two and a half years.
What do I think about the stability of the solution?
I have never encountered any stability issues for the product.
How are customer service and support?
Sometimes, the technical support team responds promptly and helps with incidents, but other times, they require multiple logs and take more time to provide root cause analysis.
How would you rate customer service and support?
Positive
What's my experience with pricing, setup cost, and licensing?
The licensing cost of Couchbase is quite expensive compared to other databases.
What other advice do I have?
The platform's migration process, including upgrades, is quite easy compared to other databases like PostgreSQL.
I rate a six out of ten.
Couchbase is a versatile and powerful database
Good to go
Easy To Use Open-Source Software
Easy to use and well documented, issues when dealing with larger data
Doesn't perform well when data increases, lot of times I get ambiguous timeout exceptions.
Couchbase UI is also very easy to use.
Not dislike but one improvement I would suggest is -
Give a builtin mechanism to handle concurrent updates to a document in db.
And with proper indexing queries works pretty fast too.