Overview
Couchbase Server is a NoSQL database that delivers unparalleled performance at scale, on premises and in any cloud. It features memory-first architecture, built-in cache, geo-distributed deployment, and workload isolation. Couchbase excels at supporting business-critical applications at scale while maintaining submillisecond latencies.
Highlights
- Multi-Dimensional Scaling (MDS): One size never fits all when it comes to scaling your business. MDS delivers revolutionary distributed architecture providing compute, storage, and processing workload partitioning to meet ever-changing requirements.
- Eventing: Couchbase Eventing enables user-defined business logic to be triggered in real-time on the server when application interactions create changes in data.
- Analytics: Use SQL++ based N1QL for Analytics to run ad-hoc analytical queries on operational data while leveraging an MPP query engine. All without impacting operational application performance by maintaining workload isolation.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
- ...
Dimension | Cost/hour |
|---|---|
c6g.xlarge Recommended | $0.662 |
r8g.large | $0.662 |
r8g.8xlarge | $1.641 |
t4g.2xlarge | $1.641 |
r6g.xlarge | $0.662 |
r6gd.large | $0.662 |
r6gd.8xlarge | $2.579 |
r6g.12xlarge | $3.319 |
r7g.large | $0.662 |
m6gd.4xlarge | $1.641 |
Vendor refund policy
We do not currently support refunds, but you can cancel at any time.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (Arm) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Additional details
Usage instructions
If using the sample CloudFormation template, you may login to the web UI with a browser to port 8091 as Administrator.
The IAM role "CouchbaseRole" grants the following access permissions:
Assume Role Permission: The role allows EC2 instances to assume it through the sts:AssumeRole action. Principal: "ec2.amazonaws.com"
Policies attached: CouchbasePolicy: Grants permissions to: Create and describe EC2 tags. Describe EC2 instances. Describe Auto Scaling Groups. Resource: All EC2 and Auto Scaling resources ("Resource": "*")
CouchbaseSecretPolicy: Grants permission to: Retrieve secret values from AWS Secrets Manager via the secretsmanager:GetSecretValue action. Resource: The resource reference CouchbaseSecret.
CouchbaseRallyParameterPolicy: Grants permissions to: Create or update parameters in AWS Systems Manager Parameter Store (ssm:PutParameter). Retrieve parameters from Parameter Store (ssm:GetParameter). Add tags to SSM resources (ssm:AddTagsToResource). Resource: All Parameter Store resources ("Resource": "*").
In summary, this IAM role gives Couchbase-related EC2 instances permissions to interact with EC2, Auto Scaling, Secrets Manager, and Systems Manager (Parameter Store) for resource management, secret retrieval, and parameter handling in the AWS environment.
Resources
Vendor resources
Support
Vendor support
This option includes a product license and Silver support. Please checkout our website at https://www.couchbase.com/support-policy/enterprise-software for details on our Enterprise support subscriptions tiers. For custom pricing or a private contract, please contact cloud_marketplace_orders@couchbase.com , for a private offer. Couchbase provides enterprises with access to 24 x 365 global support to help you in your Couchbase journey. For questions about support please reach out at
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
FedRAMP
GDPR
HIPAA
ISO/IEC 27001
PCI DSS
SOC 2 Type 2
Standard contract
Customer reviews
Flexible queries and fast indexing have transformed how I manage and retrieve customer data
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
Couchbase Enterprise is in a good state, and I have no negative reviews or suggestions for improvements.
For how long have I used the solution?
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.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Vendor analytics have become faster and complex migrations run smoothly with readable queries
What is our primary use case?
For Couchbase Enterprise , I am performing CRUD operations on vendor data, with the primary uses being filtering data, executing CRUD operations, and migrating data from another database.
I had a use case where I searched for important data across all 10,000 vendors to identify which vendor was missing which data. I performed this task twice, once with Couchbase Enterprise and once with MongoDB. When I used Couchbase Enterprise, the utility that I built worked very efficiently with no failures or lags. Conversely, when I did the same with MongoDB, I often faced connection timeouts and unresponsiveness. I am uncertain whether this was an architectural issue or a database-level issue, but we were using the same configurations. I did not face issues in Couchbase Enterprise, but I experienced them in MongoDB. Later, after increasing the timeout limit, things improved in MongoDB.
What is most valuable?
I have had several positive experiences with Couchbase Enterprise, such as being able to join two buckets or collections effectively. The N1QL language that Couchbase Enterprise supports is significantly better than what MongoDB offers regarding aggregations. While I can perform cross-collection joining in MongoDB, those lookups become quite messy with large amounts of vendor data, but with Couchbase Enterprise, it is much easier. When I perform migrations or search for missing data across approximately 10,000 vendors, the process feels very straightforward because I am using Couchbase Enterprise. The queries are much more readable and helpful, and when I switched to MongoDB, aggregations became more difficult because operations became messy and complex. Using Couchbase Enterprise feels much easier, and in terms of read performance, I find Couchbase Enterprise faster. Comparatively, I did not have to implement caching when using Couchbase Enterprise because results were faster with simple use cases that did not require much calculation, which was a beneficial feature. I also feel Couchbase Enterprise has many configurations available that I did not explore in MongoDB.
What needs improvement?
In the ecosystem, MongoDB has many communities available for finding solutions, where I think Couchbase Enterprise lacks.
When I faced issues with Couchbase Enterprise, the community support was not strong. I had to invest considerable time and effort to resolve issues. In contrast, when I faced issues with MongoDB, debugging was faster, and the community support was better. Additionally, I worked on some user interface development for a web application with Couchbase Enterprise, but MongoDB provides an intuitive interface with Compass, making it easier to run queries and understand the application's current state. I also heard from a peer about a complex multi-document transaction requiring strict consistency, which Couchbase Enterprise did not support effectively, whereas MongoDB was mature and predictable for such transactions.
For how long have I used the solution?
I have been using Couchbase Enterprise for a year.
Which solution did I use previously and why did I switch?
I have worked with Couchbase Enterprise for a year, and then I shifted to MongoDB due to licensing reasons.
What other advice do I have?
I would rate Couchbase Enterprise an eight out of ten.
Regarding this rating, based on my experiences and the use cases I worked on while using Couchbase Enterprise, I felt it was very good. I was able to understand and comfortably perform use cases, whether data migration or standard CRUD operations. In those cases, I found Couchbase Enterprise truly useful compared to the complex aggregations in MongoDB, although both have solid support. I still felt more satisfied with Couchbase Enterprise for the use cases I worked on, though this is not a generalized view.
Pricing, setup cost, and licensing are outside my area of expertise, but I am aware that we moved from Couchbase Enterprise to MongoDB due to licensing issues.
Session management has simplified user profiling and currently reduces time spent on analytics
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Couchbase Enterprise for almost ten years.
What do I think about the stability of the solution?
Couchbase Enterprise is stable.
What do I think about the scalability of the solution?
The scalability of Couchbase Enterprise is good.
How are customer service and support?
The customer support for Couchbase Enterprise is great.
How was the initial setup?
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.
Fast data persistence has reduced latency and supports real‑time telecom user session insights
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?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Document queries have transformed complex microservice data handling and now power faster responses
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.