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.
Couchbase Server
Couchbase | 7.6.3Linux/Unix, Amazon Linux Amazon Linux 2 2.0.20200904.0 Update - 64-bit Amazon Machine Image (AMI)
External reviews
131 reviews
from
and
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?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Google
Effortless synchronization and reliable performance streamline everyday operations
What is our primary use case?
I have two use cases right now. I have a shopping list app where users can share their lists, so I used the Sync feature with Sync Gateway.
In another product, I use what they call N1QL, which is a query language, and I use it to check if ads are available to show to a user. In one part of the product, I only use the Sync Gateway, and in another part, I use N1QL to query the database.
What is most valuable?
It just works. I used other products and they didn't do what Couchbase does. It works out of sight once everything is set up. When the user makes changes on their list in the app on their mobile phone, it syncs straight away. If there's an internet interruption, it resumes as soon as internet is available. I didn't have to do anything as a developer.
It's great because it's very different from MySQL where you have to update tables. With document type databases, you just say there's a new element in your document, and that's fine. It's really good to use.
What needs improvement?
What is missing is that they have a new version, Couchbase Mobile three, but they haven't really updated or provided help or documentation about what needs to change to update to the latest mobile version.
I'm looking into geospatial applications, and I know that Postgres has it more natively than Couchbase. However, I haven't done any testing yet to determine if I should switch databases or if Couchbase is fast enough with geospatial documents.
For how long have I used the solution?
I have been using the solution for nine years.
What do I think about the stability of the solution?
Over the past years, it just worked. I updated the servers and versions, and if it wouldn't work, I would look for other solutions, but for now it runs fine every day, every minute of the day. That is really the single reason I haven't looked anywhere else.
Once it's set up, it's easy to use, and there are no headaches. I would recommend it. There might be people I wouldn't recommend it to who don't know anything about Linux or how to set up servers. They might need to go a different route, perhaps to the cloud, which is easier to use.
What do I think about the scalability of the solution?
I've got millions of documents, and my servers are mostly idle, so it's really fine.
Which solution did I use previously and why did I switch?
There was a service from Dropbox about 10 years ago. Just before I switched to Couchbase, that was sunset. I tried Firebase back then. They had a sync service too, but it was only partly offline. Only partly the data was available on the device, and querying wasn't really supported. This is what I knew 10 years ago, and I didn't look at different products during those 10 years. I was really happy with Couchbase.
How was the initial setup?
I'd say it's a steep learning curve first, and there are three things to set up that take time. But once this is all done, it's really easy. There's no more maintenance or worrying that things don't work as advertised. They just work, which is a lot better than having a product that's easier to use at first but then afterwards you still have headaches, so I prefer Couchbase a lot to other products I tried in the past.
It's a lot to learn and to wire everything up, but that is with every good product, you've got to study. It's similar to studying English to speak it properly.
What's my experience with pricing, setup cost, and licensing?
I've been on the enterprise plan, and I think it was a five-figure amount a year. It turns out that I'm totally fine not having this enterprise account.
That was years ago when I had the enterprise plan, and it wasn't really stable then. I think it was around 2018. They did update, and since then, I haven't had any problems anymore.
What other advice do I have?
Currently, I only use it in a datacenter, not on AWS. The reason being is that when I started using Couchbase, they insisted on running Couchbase on bare metal servers, not on VMs or in a Docker container, so Couchbase has the full resources from a server. At the time, they didn't have any offers for AWS, such as Couchbase Capella. I'm really happy using it on premises.
I haven't used graphs yet. I use key value and document based functionality, and I actually used it 10 years ago. Now it's second nature to me.
I'll continue to explore using Couchbase, particularly looking into geospatial applications. While I know that Postgres has more native support for those uses, I haven't yet tested if Couchbase is fast enough with geospatial documents.
I rate Couchbase a nine out of ten.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Effectively navigates deployment challenges while requiring some improvements
What is our primary use case?
I can see Couchbase is being used for various use cases, primarily to enhance data handling capabilities.
What is most valuable?
The best thing about Couchbase is its versatility in handling data.
What needs improvement?
Overall as a tool, I see room for improvement in Couchbase in certain aspects.
For how long have I used the solution?
I have been using Couchbase for some time now.
What do I think about the stability of the solution?
When asked about stability issues with Couchbase regarding bugs or system breakdowns, this was specifically discussed.
What do I think about the scalability of the solution?
Regarding the scalability of Couchbase, I think it shows great potential for growth.
How are customer service and support?
For their support, I would rate them a 7 out of 10. I gave this rating because there are some areas where I think they could improve.
How would you rate customer service and support?
Neutral
How was the initial setup?
The deployment and initial setup of Couchbase is straightforward, though some people might see it as complex.
What's my experience with pricing, setup cost, and licensing?
The question was raised about whether Couchbase is completely free or if there are any hidden fees.
Which other solutions did I evaluate?
The discussion included whether Cassandra was being used in conjunction with Couchbase.
What other advice do I have?
I am a user of Couchbase and would recommend it to other people. Giving practical insights would be valuable advice for anyone new to Couchbase.
On a scale of 1-10, I rate Couchbase an 8.
Maintains consistent productivity and reliable data storage in gaming applications
What is our primary use case?
We used Couchbase as the primary data storage. Since our company was in the gaming industry, Couchbase stored data on players and related to games, levels, and similar objects for our mobile applications, aka games. There was a synchronization in place between Couchbase and another database, Elasticsearch. Some indices from Couchbase were periodically replicated to Elasticsearch.
What is most valuable?
I liked that Couchbase was stable and consistent, as much as possible with a NoSQL database. We didn't experience any downtime. Writing to the database was something we could rely on, and the database maintained reliable storage. This reliability was essential, giving us a good level of reassurance regarding data presence. Couchbase provided consistent productivity as a finished solution that worked well.
What needs improvement?
Couchbase needs to improve the consistent reliability of the replication feature. Sometimes, the replications would be delayed. This delay meant that data on another database, Elasticsearch, was not always up to date, which could be noticed in the games. Making replications more timely and consistent would be beneficial.
For how long have I used the solution?
I worked with Couchbase at my last workplace for two and a half years.
What do I think about the stability of the solution?
Couchbase was a stable solution for us. We didn't experience any downtime, and the data stayed there consistently.
What do I think about the scalability of the solution?
I would rate the scalability as ten out of ten. It was easily scalable, which is expected from a NoSQL database, and very important as player numbers could grow, so we needed to accommodate all that data.
How are customer service and support?
We never contacted tech support while I was at the company. However, we used the documentation, which was well-written and clear. I'd rate it ten out of ten.
How would you rate customer service and support?
Positive
What about the implementation team?
The DevOps team handled the implementation.
What was our ROI?
Couchbase maintained consistent productivity as a finished solution that worked well, saving us time dealing with something less efficient.
What other advice do I have?
I would rate Couchbase nine out of ten, given some small hiccups. For example, the replication feature needs to operate in a more timely and consistent manner. Overall, I would rate the solution nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Innovative
What do you like best about the product?
Couchbase Allows me cover large volumes of data making is well suitable for data managing when optimzing.
What do you dislike about the product?
Perhapes not Easy for newcomers when using this style of data management
What problems is the product solving and how is that benefiting you?
Orginization
G2 is recommendable
What do you like best about the product?
Its in-memory architecture ensures lightning-fast data access.
Scalability – Easily handles growing workloads with horizontal scaling.
Scalability – Easily handles growing workloads with horizontal scaling.
What do you dislike about the product?
Initial configuration and cluster management can be challenging
High memory and CPU usage, especially at scale.
High memory and CPU usage, especially at scale.
What problems is the product solving and how is that benefiting you?
C Supports seamless horizontal scaling to handle growing workloads
A robust solution for enterprises that are are AI adopters
What do you like best about the product?
I believe AI-driven features such as Capella iQ - it is a time-saving and helpfull tool that is making decisons taking more eficient and easy to use.
Also, the integration with others platforme like Google Cloud - are really beneficial for a Company that is having a multicloud strategy.
Also, the integration with others platforme like Google Cloud - are really beneficial for a Company that is having a multicloud strategy.
What do you dislike about the product?
Regarding the customer support - i'm not really enjoying that Couchbase is having a smaller developer community Than other platforms.
Setting up Coucbase clusters - requores specializa expertise, if you are not a having a background experience in areas like this, it is not a really ease of implementation for you.
Setting up Coucbase clusters - requores specializa expertise, if you are not a having a background experience in areas like this, it is not a really ease of implementation for you.
What problems is the product solving and how is that benefiting you?
Couchbase is helping us handle spike durig Peak seasons (like Black friday and Easteren).
Also îs helping uș building a personalized customer experience for out clients, recommended them the best Honey products that îs suitable for them. (We are selling hoeny - www.apisrom.ro)
Also îs helping uș building a personalized customer experience for out clients, recommended them the best Honey products that îs suitable for them. (We are selling hoeny - www.apisrom.ro)
My experience of using Couchbase
What do you like best about the product?
Easy to use database out of the box, but not without the downsides
What do you dislike about the product?
Steep learning curve, not so obvious AI-features
What problems is the product solving and how is that benefiting you?
The best part for me is how easy it's to integrate it with other services + how quickly it can be scaled
high price
What do you like best about the product?
not many buggs, quite fast in terms of support
What do you dislike about the product?
princy, other similar products out there
What problems is the product solving and how is that benefiting you?
helps us manage data in fast and efficient way
Very useful for company details
What do you like best about the product?
Helps me find data of companies, stakeholders
What do you dislike about the product?
A free plan includes very few functionalities
What problems is the product solving and how is that benefiting you?
Finding data for stakeholders
showing 1 - 10