Couchbase Reviews

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.

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.

We're in the middle of building out a persistent cache layer using Couchbase. That's across multiple international regions, but we have other instances where we're using it for data stores and some for its analytics features. 

There are a couple of benefits. It's cheaper than, for instance, Redis for us to implement a caching solution. 

The other benefit that I've noticed is the ability built into the tool to do data replication across the enterprise. If I've something in AsiaPac, something in NAM, and something in EMEA, I don't have to set up the infrastructure, buy the software, and buy the hardware outside of my database to be able to replicate between the three regions. That also applies to disaster recovery. It's built-in, and I just specify the bucket that I want to copy, and it works. So, price, extensibility, and scalability are the benefits of this solution.

The other benefit that we've noticed is speed-to-market. I began a PoC in October of last year, and there were four sprints in the PoC. By the end of the year, we were only expecting to be done with the first sprint, but we were already through the first sprint and about to complete the second sprint. The implementation time is very less. The biggest challenge we had was with indexes.

I was working on a game called Infinite Fleet and the backend for that particular game was written in Golang and our database of choice was Couchbase.

We were dealing with a lot of unstructured data and were leveraging the load balancing capabilities of Couchbase. The data that is stored on our Couchbase instances includes player profiles and metrics. 

We have a total of 25 developers who use it.

The main advantages were associated with it being a no SQL database. It helped us send out metrics or rewards to multiple players in our game at a very low latency. I pushed a lot of updates onto the Couchbase cluster and it performed very well. I was able to cater to 50,000 people within minutes and update our Couchbase DB very easily.

My use case of Couchbase is supporting around 920 nodes, including 420 clusters. I lead an off-shore team and my client is in the retail domain. In my current project, around 30 different applications are using Couchbase with 5 DBAs. All are e-commerce. We are customers of Couchbase and I'm a Couchbase administrator. 

A great feature is Sync Gateway, which supports the mobile application. In previous versions we had to rebuild indexes for the patching activity or the upgrade activity. The indexes automatically rebuild now once the node is added to the Couchbase cluster. Configuration in Couchbase is also quicker in comparison to the other NoSQL databases. This is a user-friendly solution. 

In the beginning, we used this solution to store configuration data. We had a system that we used for management for our platforms. We then needed a system that could help with configuration of platforms. We were looking at a couple of different options of how to store those configurations dynamically. We have 17 people that use this solution in total. 

It took us a while to figure out how to use this solution. 

I can input any kind of document into the solution and it is integrated using a dynamic API. This has been the most valuable aspect of using this solution. 

You do need something that will integrate with Couchbase separate to your front end application and we use Angular. Our APIs integrate with Couchbase using the SDKs that they have available. I mainly use their dot net SDK.

We manage our telecommunication application using the product. 

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.

Initially we were using the on-premise Couchbase Server which was maintained by the organisation with assistance from a consultant from Couchbase. After they came up with the cloud version of Couchbase called Capella, it was decided to migrate there to reduce the maintenance cost and to take advantage of the advanced features the product offers. 

Couchbase Capella offered distinct advantages like ease of horizontal and vertical autoscaling, ease of querying using the SQL++ language (which is not hard to learn), and the flexibility it offers while being hosted in the cloud and being served by the parent company.

We moved from a relational database to a non-relational database, where there is no format for storage of data, no linking of different tables, and not too much effort is required in learning the query language. This has made data storage an easier process and querying effort is optimum.