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.
Associate Principal Performance Engineer at Aptos Retail
Real User
Top 5
2024-07-30T17:00:00Z
Jul 30, 2024
Earlier services were designed to be integrated with the non-relational databases and when a different type of database is introduced it is obvious that there will be issues in integrating with the existing infrastructure. Same was encountered when trying to integrate Couchbase and exhaustive testing of the setup was done to check for data integrity. An area of improvement for Couchbase would be to integrate the 3 parts of the Couchbase server (Server, Sync Gateway and Couchbase Lite) into a single unit so the integration with the customer infrastructure becomes easier.
The platform's grouping features need improvement. Additionally, it supports only a few storage types, which presents challenges, particularly for I/O operations.
CTO Architect at a financial services firm with 10,001+ employees
Real User
Top 20
2023-01-13T01:04:37Z
Jan 13, 2023
Their security model leaves something to be desired. Their indexes could use some work, but once we found out what was going on with them, it became second. So, the biggest one so far is integrating with an external security model and having a security model that you can use. I know there's a performance hit with it, but if possible, I'd like to be able to go down to potentially a column-level instance. I'd like to be able to set up entitlements based on that. I can do that currently, but it's a little bit convoluted in the way I have to do it. It can become, from a large enterprise standpoint, a bit unwieldy in the way I have to manage it to get it to work. The other thing that they could really improve is their documentation. Their online documentation or just documentation in general is pretty bad. The online documentation is very confusing. It's not very intuitive to find information. There are no white papers on best practices for doing things. As much as everybody rags on IBM, considering the various different software products that IBM has, their documentation, for the most part, is very good. You can find many white papers, and it's very easy to find things, whereas, with Couchbase, the whole documentation setup is very confusing. It's not usable, for the most part. They should support native S3 ingestion into the default bucket or into the system. Currently, when I want to look at S3 stuff, I use the analytics engine, and that works fine. However, when I want to use S3 as a landing point to be able to load into the default Couchbase—not use in the analytics engine but just to import into Couchbase—there's no native way of having Couchbase talk to S3 to get JSON documents out and loaded into the data store. So, I've to use a third-party product called Data Sync to be able to pull stuff out of S3. The integration options aren't as robust as they probably need to be. They only have about two. It's easy to deploy. Where the challenge comes in is when you start putting data in, doing the indexes, and doing the integration with systems. Integration is one of their weakest points. Natively, there should be a wide range of integration options to be able to get data in. Once you get the data in, it's really easy to get the data out. It's very simple. It's a JDBC, etc. It's just that the integration to get the data in can be a challenge.
Backend Developer & Team Lead at Osiris Trading powering Betway
Real User
2022-12-21T14:56:30Z
Dec 21, 2022
The scripting language for this solution could be improved. A big selling point is that they're like SQL server but there is still quite a lot of missing functionality. They are slowly adding additional functionality but without it, the solution ca be complex to use. Secondly, this solution does not function well on a Windows based server or infrastructure. Hosting it on a Windows server can max out your CPU and bring down your cluster. This is one of the main reasons that we stepped away from having that in this kind of environment as well as needing to buy a license for support. There is also a lack of documentation.
Chief Technology Officer at a comms service provider with 1-10 employees
Real User
2022-03-09T16:34:59Z
Mar 9, 2022
We would like to have a better management of Kubernetes with the free, open source version of Couchbase. We don't have any major complaints other than that.
There are some limitations to the database. The SQL database cannot handle real-time processing for critical IoT scenarios. What we have to do is store our data into the database then code it out, this wastes a lot of time.
Most of the time, the only issued that I have faced was when we upgraded the Couchbase version. It is very difficult to load the backup of the older version to the newer version. The only problem with it, I mentioned, the loading data from a different version. For that, we use replication to solve the issue. This is the only bad issue we faced, otherwise it is perfect.
Chief Information Officer at a computer software company with 51-200 employees
Real User
2018-12-11T08:31:00Z
Dec 11, 2018
The failover and failback could be a bit easier. When I looked at it last time, it had to be manually done. It also took over an hour for us to rebalance all the nodes.
Couchbase is a versatile database solution for healthcare, automation, e-commerce, gaming, caching, and analytics. It supports 920 nodes and 420 clusters, making it scalable and extensible. Its valuable features include multiple database paradigms, low latency, dynamic API integration, Sync Gateway for mobile apps, and a user-friendly interface.
Couchbase has helped organizations with low latency metrics, large user updates, and cost-effective caching. Its built-in data replication and...
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.
Earlier services were designed to be integrated with the non-relational databases and when a different type of database is introduced it is obvious that there will be issues in integrating with the existing infrastructure. Same was encountered when trying to integrate Couchbase and exhaustive testing of the setup was done to check for data integrity. An area of improvement for Couchbase would be to integrate the 3 parts of the Couchbase server (Server, Sync Gateway and Couchbase Lite) into a single unit so the integration with the customer infrastructure becomes easier.
The platform's grouping features need improvement. Additionally, it supports only a few storage types, which presents challenges, particularly for I/O operations.
Their security model leaves something to be desired. Their indexes could use some work, but once we found out what was going on with them, it became second. So, the biggest one so far is integrating with an external security model and having a security model that you can use. I know there's a performance hit with it, but if possible, I'd like to be able to go down to potentially a column-level instance. I'd like to be able to set up entitlements based on that. I can do that currently, but it's a little bit convoluted in the way I have to do it. It can become, from a large enterprise standpoint, a bit unwieldy in the way I have to manage it to get it to work. The other thing that they could really improve is their documentation. Their online documentation or just documentation in general is pretty bad. The online documentation is very confusing. It's not very intuitive to find information. There are no white papers on best practices for doing things. As much as everybody rags on IBM, considering the various different software products that IBM has, their documentation, for the most part, is very good. You can find many white papers, and it's very easy to find things, whereas, with Couchbase, the whole documentation setup is very confusing. It's not usable, for the most part. They should support native S3 ingestion into the default bucket or into the system. Currently, when I want to look at S3 stuff, I use the analytics engine, and that works fine. However, when I want to use S3 as a landing point to be able to load into the default Couchbase—not use in the analytics engine but just to import into Couchbase—there's no native way of having Couchbase talk to S3 to get JSON documents out and loaded into the data store. So, I've to use a third-party product called Data Sync to be able to pull stuff out of S3. The integration options aren't as robust as they probably need to be. They only have about two. It's easy to deploy. Where the challenge comes in is when you start putting data in, doing the indexes, and doing the integration with systems. Integration is one of their weakest points. Natively, there should be a wide range of integration options to be able to get data in. Once you get the data in, it's really easy to get the data out. It's very simple. It's a JDBC, etc. It's just that the integration to get the data in can be a challenge.
One thing that could improved upon is the level of concurrency. The documentation for this solution could also be improved.
The scripting language for this solution could be improved. A big selling point is that they're like SQL server but there is still quite a lot of missing functionality. They are slowly adding additional functionality but without it, the solution ca be complex to use. Secondly, this solution does not function well on a Windows based server or infrastructure. Hosting it on a Windows server can max out your CPU and bring down your cluster. This is one of the main reasons that we stepped away from having that in this kind of environment as well as needing to buy a license for support. There is also a lack of documentation.
We would like to have a better management of Kubernetes with the free, open source version of Couchbase. We don't have any major complaints other than that.
There are some limitations to the database. The SQL database cannot handle real-time processing for critical IoT scenarios. What we have to do is store our data into the database then code it out, this wastes a lot of time.
Most of the time, the only issued that I have faced was when we upgraded the Couchbase version. It is very difficult to load the backup of the older version to the newer version. The only problem with it, I mentioned, the loading data from a different version. For that, we use replication to solve the issue. This is the only bad issue we faced, otherwise it is perfect.
I have tried multiple libraries in a demo they provide and it works fine, but when it merges with libraries, it creates a problem.
The failover and failback could be a bit easier. When I looked at it last time, it had to be manually done. It also took over an hour for us to rebalance all the nodes.