Couchbase Enterprise Reviews

My main use case for Couchbase Enterprise is the way it gives us low latency and operational analysis, and it also helps us in fraud detection, so these are the main use cases of Couchbase Enterprise. The ability to work with unstructured data and search the unstructured data are additional important aspects.

For a fraud detection example, we are using a JSON-based database where, suppose someone has made a transaction, and we need to track it down.

Couchbase Enterprise helps in the detection of abnormal, suspicious behaviors in a transaction by comparing against expected patterns, allowing us to query based on if the transaction amount is greater than one lakh or if the same card is used within two countries within a short amount of time, such as two minutes or one minute. More short or repeated transactions can help to identify fraud detection.

Talking about the best features of Couchbase Enterprise, I think that the data is served from RAM first and not on the disk, making it low latency and extraordinarily fast for read and write, which is ideal for real-time apps. The model provides key-value, ultra-fast search, and also JSON document and SQL-like query, N1QL, which are very helpful. There is built-in caching and persistence in the data, keeping data in memory while also persisting on the disk for fast querying. The system also has index search and indexing for optimized search, and I feel these features really stand out.

The key-value search is the feature I use most day-to-day, while indexing works in the background. We can query based on the index; together, these two features make it faster. I would also mention the enterprise-grade security, including role-based access control, encryption, and auditing, which stand out as well.

Couchbase Enterprise has positively impacted my organization by making data querying faster, and real-time analytics is also done effectively.

One thing is that better adoption should be there among users, so we can work on this, and a proper learning path should be provided by Couchbase for more adoption.

More documentation should be available easily, and a better connection with other enterprises such as Microsoft Fabric should be established.

I have been using Couchbase Enterprise for more than one year.

Couchbase Enterprise is stable in my experience.

Scaling with Couchbase Enterprise is easy, as it supports horizontal scaling, making it straightforward to scale up or down as our needs change.

Currently, there is no business relationship with Couchbase other than being a customer, but my previous company, which was Silver Technology, had one, although I am currently working in a different organization.

We were previously using other solutions before Couchbase Enterprise.

We manage and monitor Couchbase Enterprise in our environment using the built-in admin console and REST API in Couchbase Server Enterprise Edition for cluster management, and we automate it using CI/CD for development and configuration. For monitoring, we track performance using Couchbase UI metrics.

I see a return on investment with Couchbase Enterprise because the query processing is fast, leading to a financial impact with additional revenue per year for the organization, alongside benefits based on the database and productivity. The productivity of my team has also increased due to the fast processing.

My experience with pricing, setup costs, and licensing for Couchbase Enterprise has been quite good.

We evaluated other options such as SQL Server and MongoDB, and we also considered Cassandra before choosing Couchbase Enterprise.

I have not gotten an opportunity to work on real-time triggers, such as fault alerts and notifications on data pipelines, so these are features I want to explore more in Couchbase Enterprise.

My advice would be to switch to Couchbase Enterprise as early as possible because it is faster, and the ROI is good when investing in Couchbase Enterprise. It has a RAM-heavy design that supports real-time and high-throughput operations. I would rate this review at a 9.

Public Cloud

Microsoft Azure

Our primary use case for Couchbase is related to the iGaming industry, particularly for high-performance reads and writes to meet our SLA for high volumes. We have a particular use case where there is an SLA of one second, and Couchbase is critical for ensuring our wallet operations function correctly.

Couchbase, being a multi-master solution, allows us to process more load and has enabled us to scale more significantly with lower costs, especially under high user spikes.

The most valuable features of Couchbase include the key-value storage due to its speed and the multi-master capability, which provides more speed and scalability compared to master-slave databases. 

The support for syntax that allows reading by properties sets Couchbase apart from alternatives like Redis. Additionally, Couchbase's N1QL query language minimizes the learning curve for developers, facilitating an easier adaptation to the technology.

I would like Couchbase to provide more functionality via the UI, as some operations, such as time-based scaling, currently require using the API. While I find Couchbase's feature set to be generally satisfactory, adding more UI-based configuration options would be beneficial.

I have used Couchbase for four years.

Couchbase is highly stable, rated at nine out of ten. 

Stability is crucial as it prevents users from turning to competitors.

Couchbase is extremely scalable, which is critical when handling high throughput and load. 

I rate its scalability at ten out of ten.

I rate customer service at ten out of ten. The support team has been helpful with VNET configuration, Sync Gateway, and other technical issues.

Positive

We previously used Mongo database but switched to Couchbase since it is a multi-master solution, allowing us to process more load and scale with lower costs.

The initial setup is quick with Couchbase Capella, taking about 30 minutes. Deployment on Kubernetes or VMs may require about half a day for setup.

Typically, one person is sufficient for deployment, especially with Couchbase Capella. For in-house deployment, one or a maximum of two people can handle the configuration.

Investing in Couchbase has significantly lowered our operational costs and increased throughput, reducing costs by half and supporting around five times the non-peak user volume during peak hours.

The pricing of Couchbase varies depending on the usage. It can range between 25,000 to 40,000 Euros per year depending on company requirements.

We evaluated Mongo database but chose Couchbase due to its multi-model flexibility and the advantages of being a multi-master database.

Couchbase, especially under high load conditions, is imperative for providing a great user experience due to its stability and scalability, which reduces costs and scales efficiently. 

I rate Couchbase at nine out of ten.

Public Cloud

Other

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.

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.

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.

Our team has been using Couchbase for a while, but I started using it only in the last year.

We encounter compatibility issues with JDK and similar technologies whenever we perform upgrades. We had some issues recently.

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.

Positive

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.

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.

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.

Hybrid Cloud

Google

My main use case for Couchbase Enterprise is to store data according to our requirements in our telecom-based company to manage, store, and retrieve information from the database. After two years of using Couchbase Enterprise, I find it very good. Being a NoSQL database, it allows for easy data storage and retrieval. I primarily use Java Spring Boot and make use of Couchbase Enterprise POM as well.

A specific example of how Couchbase Enterprise helped me manage and retrieve data efficiently is when I create a customer by gathering all relevant information such as name, email, and phone number, and I utilize the CRUD repository in the Java code to store it in Couchbase Enterprise. I call the save method to store the created records, triggering the API from the backend, which then stores the data in the repository, reflecting my basic flow.

Regarding my main use case with Couchbase Enterprise, I can share that in the Couchbase Enterprise GUI, I utilize N1QL for searching using meta queries, which is very helpful for running queries. Unlike MongoDB, where writing complex queries is necessary, Couchbase Enterprise allows me to directly write SQL queries to retrieve data easily, and this has been a very good experience.

The best features Couchbase Enterprise offers in my experience include the indexing part, which I find very beneficial. In the Couchbase Enterprise GUI, creating indexes is straightforward as I have learned from YouTube and the documentation, making it easy. I also appreciate the caching part, so I am not using additional tools like Redis.

In terms of performance, Couchbase Enterprise is very good and fast to retrieve and manage data, although I have not explored much else.

Couchbase Enterprise has positively impacted my organization by being a positive point for data management, although I am not certain about specific metrics like productivity or cost savings as I do not have insight into that being an employee.

Couchbase Enterprise is in a good state, and I have no negative reviews or suggestions for improvements.

I have been working in my current field for a total of two years, which includes one year of internship and one year of full-time employment.

I do not have any thoughts on the pricing, setup cost, and licensing for Couchbase Enterprise as these matters are managed by the DevOps team. I am a developer and only receive credentials and access.

My advice for others looking into using Couchbase Enterprise is that it offers a lenient learning curve compared to many databases in the market. It combines features of both MongoDB and SQL, making it easier for developers to work with JSON data and write queries in a straightforward manner using N1QL.

Public Cloud

Amazon Web Services (AWS)

My main use case for Couchbase Enterprise is to store sessions. Specifically, I utilize the product's session management function to store user experience sessions in Couchbase, and for the profiles so that I can discover the peer node. For long timers, I use Couchbase Enterprise.

A specific example of how Couchbase Enterprise fits into my session management and profile discovery processes is that the session management of the discovery profile functions in distributed systems, where the peer node can change, meaning it's not systematic data that can be stored. Therefore, Couchbase Enterprise is a perfect solution for me to store that session in the database.

The best features Couchbase Enterprise offers for my use cases are user profile and session management.

For user profiles and session management, the features of Couchbase Enterprise that make it stand out for me are its scalability, performance, and flexibility. I would add that Couchbase Enterprise is reliable; being a key-value store makes it especially useful for me. Additionally, it can be set up on Azure, AWS, or on-premise, which is a great feature.

Couchbase Enterprise has positively impacted my organization by being easy to set up and use, making the GUI perfect for everyone, which enhances user experience. This ease of use translates into actual outcomes, such as saving my team time for analytics. The GUI saves me a lot of time since I can directly check the document in the key-value store in JSON format, which allows anyone to access it. Consequently, that reduces team time and errors, with measurable benefits.

There is room for improvement from a perspective of needing enhancements. Couchbase Enterprise is fine and working well, so I do not see much improvement needed from the organizational perspective of where I am working or on the product I am using. The reason I chose nine out of ten is that there should be a dedicated feature that allows it to come up with a single click for the ease of everyone, which is why I leave that one point off.

I have been using Couchbase Enterprise for almost ten years.

Couchbase Enterprise is stable.

The scalability of Couchbase Enterprise is good.

The customer support for Couchbase Enterprise is great.

Negative

Couchbase Enterprise has positively impacted my organization by being easy to set up and use, making the GUI perfect for everyone, which enhances user experience.

On-premises

Other

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.

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.

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.

I worked with Couchbase at my last workplace for two and a half years.

Couchbase was a stable solution for us. We didn't experience any downtime, and the data stayed there consistently.

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.

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.

Positive

The DevOps team handled the implementation.

Couchbase maintained consistent productivity as a finished solution that worked well, saving us time dealing with something less efficient.

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.

Public Cloud

Amazon Web Services (AWS)

In my company, we use the enterprise version of Couchbase, and it is used across the organization for its database operations. We do only use the NoSQL database, not Couchbase Capella.

The tool is mostly for document-based storage of Cisco, which is a retail company. We manage a lot of product information and send a lot of metadata that we generate for all of our orders, including baskets and other aspects. We use Couchbase heavily for document-based storage purposes.

The most valuable feature of the solution stems from the ease of operation with Couchbase, and it has a lot of extensive features that it provides because it's not a document-based storage. We can also do basic operations on those documents, like indexing important fields, a full-text search, and advanced machine learning operations, like vector search. The tool is pretty easy to use and work with as it is a schema-less tool, so we don't have to work too much on defining the schema for the tables or the documents. It is very easy to onboard the tool to work for the new teams. It is a very extensible tool. My company gets a lot of good support from them as well, and their documentation is also pretty good, which we have found. Compared to other tools, such as the best document-based storage, MongoDB, and others, Couchbase works pretty well. Couchbase also provides good offerings in terms of the different features that we need from different DBs, like searching operations and materialized views. The tool works pretty well. The tool also provides very good latency on high loads. The scalability and the reliability are also other important aspects of the tool.

With some of the operations, we used to face some challenges with scalability. Although it worked pretty well, in some scenarios, we noticed issues where the replications and the sharding were not happening correctly. In recent versions, we also faced some issues in terms of enabling advanced operations like FTS and vectors. Although it works pretty well, in some places, we do face challenges, especially on a heavy scale. I think all issues are being addressed in the latest version of Couchbase.

The resources are not that good for Couchbase. The tool's documentation is pretty extensive, but if you go for any kind of courses or tutorials, there are very limited resources available. It also becomes a little bit challenging for new people to get onboard into it. MongoDB and other such open-source database tools perform really well as they're really widely adopted, and they have resources available to get you onboarded pretty quickly. I think that we do face some challenges with Couchbase, but luckily, we have the tool's enterprise version solution, so we get all the support from the product team.

I have been using Couchbase for two or three years. I am a customer of Couchbase.

I rate the technical support a nine out of ten.

Positive

The product's initial setup phase is easy.

The solution can be deployed in two to three minutes.

I suggest the tool to others as it is heavily, working a lot on improving the database framework.

The tool offers support for multiple data models.

We do need to maintain the tool as there is a need to upgrade it, and we do need to do continuous patching. We do have a central team for Couchbase, and they manage it for us. They are actively working with Couchbase's enterprise team to do all those operations, like patching, server upgrade, and backup, but it all requires some kind of support.

The tool has some AI capabilities, as you can do vector search, semantic search, groupings, and using open-source models and enabling them on the database so that we can structure our data better and do things like advanced search operations.

I rate the tool an eight out of ten.

I can see Couchbase is being used for various use cases, primarily to enhance data handling capabilities.

The best thing about Couchbase is its versatility in handling data.

Overall as a tool, I see room for improvement in Couchbase in certain aspects.

I have been using Couchbase for some time now.

When asked about stability issues with Couchbase regarding bugs or system breakdowns, this was specifically discussed.

Regarding the scalability of Couchbase, I think it shows great potential for growth.

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.

Neutral

The deployment and initial setup of Couchbase is straightforward, though some people might see it as complex.

The question was raised about whether Couchbase is completely free or if there are any hidden fees.

The discussion included whether Cassandra was being used in conjunction with Couchbase.

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.