Reviews from AWS customer

6 AWS reviews

External reviews

142 reviews
from and

External reviews are not included in the AWS star rating for the product.


4-star reviews ( Show all reviews )

    Andlib Saif

Distributed workflows have improved real-time validation and now deliver faster, reliable testing

  • April 05, 2026
  • Review from a verified AWS customer

What is our primary use case?

I have used Couchbase Enterprise in a different way. I used it in Informatica to set up an end-to-end flow for the connector. Informatica used to connect to Couchbase for all three applications: IICS Cloud and Informatica.

Couchbase is running on a Linux server, then I connected using Informatica connectors and evaluated how the connector works with different bucket sizes. I focused on low latency using high-performance NoSQL stores, data validation, integrating Couchbase with PySpark and Great Expectations. I performed end-to-end API and database testing, including event-driven testing. Mostly, I used it for distributed system testing.

I integrated a workflow as a core data store within a data pipeline for QA validation. Couchbase Enterprise acts as my primary NoSQL database for storing JSON documents such as orders and users. The API interacts directly with Couchbase Enterprise for low latency read and write operations. I validate API responses versus database data consistency and data correctness after business operations. For data pipeline validation, I use PySpark to extract data from Couchbase Enterprise for large-scale validation, which is useful in ETL data engineering workflows. I then use data quality automation with Great Expectations where I perform data quality checks such as schema, null, range, and business rules validation. For end-to-end testing, I verify whether all data and subsequent data landed into the target correctly from source to database. I also tested distributed system scenarios including failover, recovery, rebalancing, replication, and load balancing to ensure the cluster responds correctly without any data loss when a node goes down. I then evaluated query performance across these scenarios.

What is most valuable?

Couchbase Enterprise offers sub-millisecond response times with built-in memory cache and storage in the storage engine. Rebalancing plus failover are valuable, and the platform supports key-value, multi-model database functionality including key-value support, SQL query, JSON documents, full-text search, and analytics. I can perform relational operations such as joins and aggregations with indexes. Built-in replication, high availability, VBucket system, automatic failover, and cross data replication are all valuable features. There is also mobile edge support and offline sync capability. Enterprise-grade security includes audit logging and compliance with HIPAA and PCI standards. The vector search feature is also a valuable addition.

In my day-to-day work, I mainly use SQL transactions and SQL queries combined with proper indexing because it helps me perform easy validation and fast debugging. Indexing enables strong data validation and increases performance. Support for joins and aggregation helps in defining relationships across the database, and these are the standout features I use.

The best features are high availability, failover, replication, VBucket, and XDCR, which stand out in handling failures without impacting the application. Data is always stored with a replica copy. If a node fails, replica VBuckets are promoted automatically with no data loss and minimal service disruption. This gives me strong confidence and is critical for distributed systems, disaster recovery, and geo-distributed applications. For someone working on data validation and distributed systems, this provides confidence that even under failure conditions, the system maintains data integrity and availability. In addition to SQL++ query capabilities, I really value Couchbase Enterprise's built-in high availability and failover mechanism, the way it handles replication and automatic failover.

For the enterprise, we have faster read and write latency and real-time use cases with fewer bottlenecks. Couchbase Enterprise combined with a database, cache, and query engine helps in faster retrieval of queries and it is a single platform that handles everything. SQL++ query can quickly validate back-end data and debug issues faster. It integrates with PySpark and Great Expectations, so schema validations and data quality rules can be handled much earlier. Built-in failover, replication factor, and failover mechanisms give minimal downtime and high confidence during deployment. Scalability is a major factor as it can scale very easily.

Couchbase Enterprise has significantly improved performance and enabled real-time data access while simplifying our architecture by combining cache and database capability. It has enhanced data validation and testing efficiency through SQL++ query, and its built-in scalability and high availability have allowed us to grow workload reliability with minimal downtime. The cache layer combined with Couchbase Enterprise database cache plus query layer has reduced infrastructure and maintenance cost by twenty to thirty percent with fewer licenses, fewer servers, and less operational overhead. Faster API response due to in-memory architecture and efficient indexing provides better user experience and higher throughput. Reduced debugging time and issue resolution time by forty to fifty percent. PySpark integrated with Great Expectations has improved automation efficiency and reduced manual effort of database checking. Horizontal scaling has improved deployment and scalability speed. From a cost and efficiency perspective, Couchbase Enterprise has helped reduce infrastructure and operational costs and consolidated multiple systems into a single platform. We saw a two to five times improvement in API response and debugging time reduced to nearly five percent. Automation saved about thirty to forty percent in data validation time.

What needs improvement?

Bucket concepts such as bucket, scope, collection, VBucket are very new to users and take time to understand. Better guided onboarding and simplified documentation with real-world examples could help. Index complexity and management including choosing the right index, managing index fragmentation, and memory overhead could be improved. Smarter index recommendations using AI-driven analysis and better visualizations, data lineage, and understanding of data flow could help users understand how things work. RAM quota, index service memory, and data allocation issues can impact performance and could be solved with more automation of resource optimization. Better cost and performance recommendations can be provided.

Replication lag, failover behavior, and rebalancing issues could benefit from better observability, a more intuitive dashboard, or root cause analysis capability. A dashboard to track licensing and cost would make users aware of their consumption. End-to-end query tracing would be helpful because in real-time projects, creating and dropping indexes through query services and indexing services does not always have obvious performance impacts. Switching between dashboard logs to correlate query latency, index scanning time, and node resource usage takes considerable time.

During scaling or node replacement, rebalancing takes time and system performance can degrade temporarily. More adaptive and throttled rebalance with minimal impact may help. In addition to using Great Expectations, built-in data quality checks within Couchbase Enterprise would help in identifying end-to-end data quality issues. Error reporting and analysis can be improved significantly, which will help in reducing debug time.

For how long have I used the solution?

I have been using the solution for around six to seven years.

What do I think about the stability of the solution?

Couchbase Enterprise is stable. This is why we are continuing to work with it and building a connector on top of it. There are no significant issues with Couchbase Enterprise. It is a reliable production environment and a good product.

What do I think about the scalability of the solution?

Horizontal scaling has been very good. Even with multi-dimensional query levels, vertical scaling has been efficient and cost optimization has been achieved.

How was the initial setup?

I would say the setup is moderately easy. Cluster setup, UI, and basic configuration were straightforward. What was challenging was production-level configuration, index planning, AWS integration, and the learning curve for the team in scaling operations.

What other advice do I have?

Organizations that Couchbase Enterprise is best suited for include medium to high e-commerce companies, streaming services, some financial companies, though banking may not be the primary focus. Mobile-first, SaaS, and microservice-based companies are ideal candidates.

I will definitely recommend Couchbase Enterprise to others as it handles high performance, scalability, and real-time data handling effectively. I gave this review a rating of eight 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?


    Ishan Thakur

Fast data persistence has reduced latency and supports real‑time telecom user session insights

  • February 24, 2026
  • Review from a verified AWS customer

What is our primary use case?

Since I joined the company, I have been using Couchbase Enterprise because the company was experiencing latency issues with SQL databases and wanted to shift to a NoSQL fast persistence solution, which led us to Couchbase Enterprise.

We use Couchbase Enterprise to store user data, as Mobilium is in the telecom domain, and we store telecom-related data such as user profile information, applicable rate plans, PCC rules, and user location information.

I worked in a 4G project related to the Gx interface, where we store session data in Couchbase Enterprise, and we also store the usage done by the subscriber in Couchbase Enterprise.

We also store session data for web services and analytical data in Couchbase Enterprise.

What is most valuable?

Couchbase Enterprise offers features such as horizontal scalability, providing high availability and performance, and it also includes XDCR replication, which is a great feature.

Based on my experience, the Couchbase Enterprise UI is very helpful for debugging issues, and there is a way to transfer data from one server to another, which is very helpful in development to speed up the development process.

Previously, we used SQL persistent databases, which were not optimized, but since the company shifted to Couchbase Enterprise, the application latency decreased by 70 to 80%, helping the organization attract better clients. Working on a telecom project, we migrated the core logic of the application from SQL persistent database to Couchbase Enterprise, which decreased the application's latency by 70 to 80%, attracting high-profile clients and significantly boosting revenue.

What needs improvement?

I would appreciate seeing faster index building in Couchbase Enterprise; while enhancements have been made in version 8.0, users frequently look for even faster secondary index builds to reduce bottlenecks during high-volume operations, along with improved rebalance efficiency and continued refinement of the empty node batching technique.

For how long have I used the solution?

My name is Ishan Thakur, and I work as a software engineer in Mobilium India Private Limited.

What do I think about the stability of the solution?

Couchbase Enterprise is very stable.

What do I think about the scalability of the solution?

Couchbase Enterprise's scalability is very good, as it supports horizontal scaling, allowing us to add more servers.

How are customer service and support?

Customer support for Couchbase Enterprise is very good.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

Previously, we used an Oracle database and switched due to latency issues.

What's my experience with pricing, setup cost, and licensing?

From my seniors, I have heard that the money needed for the architecture was reduced after using Couchbase Enterprise, though I am not aware of the specific details.

What other advice do I have?

I would rate Couchbase Enterprise an eight.

I gave it an eight because Couchbase Enterprise offers very good features, such as high availability due to its cluster architecture, XDCR replication, and a good UI for debugging issues; plus, it also provides an SDK to interact with Couchbase Enterprise.

If someone is looking for very efficient and fast NoSQL data persistence, then Couchbase Enterprise is the product I would recommend.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?


    Meghnaja Jaswani

Document queries have transformed complex microservice data handling and now power faster responses

  • February 23, 2026
  • Review from a verified AWS customer

What is our primary use case?

Couchbase Enterprise serves as our primary solution for persisting data into the database, and as a document-based data structure, it is one of the efficient solutions for our architecture.

For example, I had one of the microservices, Product Inventory Sync, and for that, we used particular documents which were first persisted into Couchbase Enterprise; these were Product Inventory Loader documents, and based on ID, it was very easy for me to search and find particular records in our database once they were persisted.

Another scenario related to customer service is the billing account service, where in multiple domains and subdomains we use Couchbase Enterprise, and we chose it for its inbuilt cache, which helped us significantly with performance; additionally, we were able to write queries on top of that and retrieve our data based on customer ID, billing account ID, and various other parameters, allowing easy data searches from Couchbase NoSQL database.

What is most valuable?

The best features Couchbase Enterprise offers that stand out for me are that we can write SQL queries, search based on ID, and it has inbuilt cache; these features helped us significantly in our e-commerce-related domain with complex structures in the form of JSON data, making it easy to persist complex data structures that include products, features, nested features, characteristics, and external identifiers.

Couchbase Enterprise has positively impacted our organization by reducing latency by 60%; with its inbuilt cache, our performance improved significantly by 50%, and the time taken to search in Couchbase was also reduced, leading to an overall performance improvement of 78.3%. We measured those improvements based on production logs, identifying that a microservice which originally took around six seconds now takes 800 milliseconds, a great optimization noticed by customers, especially during traffic spikes where the response to requests was significantly faster compared to the earlier case of six seconds, using the ELK stack in production along with Kibana and Splunk logs for tracking.

What needs improvement?

Couchbase Enterprise is a great product overall, however I suggest improvements as there were some instances when retrieving data was slow, especially for a few created buckets on localhost and in production, but these were rare occurrences.

Regarding needed improvements, I would address documentation and integration issues, as it is unclear why Couchbase Enterprise is not as widely discussed as MongoDB despite being a capable NoSQL database, likely due to less clear documentation and somewhat difficult integration processes.

For how long have I used the solution?

I used it for more than three years.

What do I think about the stability of the solution?

Couchbase Enterprise is absolutely stable.

What do I think about the scalability of the solution?

Couchbase Enterprise is very efficient in handling growth and increased workloads, proving to be effective during traffic spikes and addressing any problems with horizontal scaling.

Which solution did I use previously and why did I switch?

Previously, we used an Oracle database, which was based on a monolithic architecture that was difficult to maintain due to complex hierarchy related to e-commerce, including product orders and multiple tables and joins, which is why we switched to Couchbase Enterprise as a great solution.

What was our ROI?

We have indeed seen a return on investment with Couchbase Enterprise, as it allowed us to save costs by using it for all services, which improved interaction efficiency with microservices and reduced persistence time by 60%, resulting in good profits by providing efficient services to clients.

What's my experience with pricing, setup cost, and licensing?

My experience with pricing, setup cost, and licensing has been fair, and I am satisfied with what the services provide, considering that setup costs and licensing have been reasonable when comparing the services offered.

Which other solutions did I evaluate?

Before choosing Couchbase Enterprise, we did evaluate other options, including MongoDB, which is widely recognized as one of the market's leading NoSQL databases.

What other advice do I have?

One additional feature to mention is that while working on the PI Sync microservice, we used Elasticsearch alongside Couchbase Enterprise, which provided us with the whole call stack, and in Couchbase Enterprise, the whole document was persisted, which included the complete stack trace for failures, allowing us to easily retrieve those PI Loader documents and persist related events in the database.

My advice for others considering Couchbase Enterprise is that it is easy to deploy and user-friendly; it connects well with microservices locally, making it simple to retrieve and persist documents in production.

I highly recommend Couchbase Enterprise for anyone considering it, especially for use cases involving complex JSON structures, as it is both cost-effective and user-friendly. 

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?


    reviewer2702670

Maintains consistent productivity and reliable data storage in gaming applications

  • May 06, 2025
  • Review from a verified AWS customer

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?


showing 1 - 4