Couchbase Server Reviews

Couchbase Server's main use case for our organization is storing data in JSON format where we have the document ID we need to store. If data is in JSON form, we can use Couchbase Server, and it will provide a cache layer before storing the data. We are primarily using Couchbase Server to store JSON data itself, but there are many more usages. It is a NoSQL distributed database built on low latency and high throughput. We can store various data such as user sessions, preferences, and profiles.

Couchbase Server is particularly useful for user sessions and preferences. A session is commonly used to store temporary data for login purposes. Whenever a user enters their credentials, we first validate them. If validation is successful, we generally store the session information in the backend. The data that the user provides is in JSON form, where we can set the user ID, username, login time, and all related information. We store the data using a key prefix, which is session colon session ID, with the session ID generated in the Java backend. We set a timeout, and if we set any timeout, such as 50 minutes, the session will expire after that time, requiring the user to send the data again. We are also using an index to store query information.

In my current project, I have been working in the airline domain, so if a user is changing or rescheduling any ticket information, we need to send all modification information to our timers. Currently, we are using Couchbase Server as the primary database, where we need to store settings to perform operations in our project. We store settings in a way that identifies the records with a document ID provided by Couchbase Server. Couchbase Server's primary benefit is that our data is in JSON form, and it is very fast in comparison to saving and retrieval with low latency. We don't need to write extensive queries to fetch data; we write any Couchbase Server repository, and if we add that find by ID or something similar, it will fetch everything in less time.

Couchbase Server offers several valuable features, including the ability to store flexible JSON documents with any structure, and it provides an in-memory architecture with first reading, then writing capabilities. We can apply auto-scaling in Couchbase Server by adding multiple nodes, which automatically distribute the data across nodes while having built-in cache. When Couchbase Server is built, they provide a disk to store and cache together, so if data is in the cache, it will not hit the database directly; instead, it will fetch data from the cache.

Whenever we use SQL Server, we use queries to fetch data. Similarly, Couchbase Server provides N1QL queries for data retrieval. In terms of security features, Couchbase Server offers role-based access control with automatic encryption and TTL timeout settings for automatic destruction upon reaching the time limit. The security capability includes role-based access control at the bucket level and essentially at the scope level, granting access based on defined roles. It also supports various authentication types, including built-in username and credential systems and LDAP.

Couchbase Server has positively impacted my organization as every company deals with data, which we are storing in Couchbase Server. When a user interacts with Couchbase Server for the first time, it fetches data from the database and stores it in the cache, so subsequent hits fetch directly from the cache without going to Couchbase Server. We don't need to explicitly set any caching technology such as Redis or Hazelcast since it has its own cache, making Couchbase Server retrieval for data purposes comparable to others.

With one year of experience, I can suggest improvements for Couchbase Server. From what I have used, it is pretty good compared to other databases, especially since our data is in JSON format. It would be a great improvement for Couchbase Server to support various data structures beyond JSON, as supporting heavy complex queries would enhance its competitive edge. Allowing different formats would be beneficial.

Regarding needed improvements, I can note any technology associated with Couchbase Server. Recently, I used Java with Couchbase Server in my project, where Java provides documentation that we can utilize. Currently, we are embedded with Couchbase Server, and Spring has made a Couchbase Server repository for integration purposes.

To improve user experience, it would be beneficial for Couchbase Server to support various data structures, enabling compatibility with formats such as PDF, JSON, XML, and others.

Supporting every kind of data structure would be a substantial improvement for Couchbase Server.

Recently, I have used Couchbase Server in my current company, and I have served one year completely in Couchbase Server.

In my experience, Couchbase Server is stable. While complex queries may take time, I have not encountered any significant issues, and I can say it is very stable as of now.

Couchbase Server's scalability meets our needs, handling growth and changes in workload well. We employ auto-scaling based on memory utilization and health, enabling it to automatically scale, which is very helpful.

I changed organizations, where Couchbase Server is used because our data is in JSON format and structured accordingly. In my previous role, we utilized a SQL database as our data was interdependent, but now, the JSON format is sufficient for our needs. The choice ultimately depends on the structure of data since relational databases are better suited for data with inherent relationships.

Whenever we are dealing with a dashboard, we can use time annotations to calculate performance metrics. Currently, we are using GCP as a cloud service. We can add time rotation, so if we want to check performance or method outputs, we can utilize system.current time to measure the start and end time for the query operation, which depends on the complexity of the method. Optimized methods yield results in milliseconds, while more complex queries might take longer. I cannot provide an exact estimate, as it all depends on the data complexity. Using an index for frequently accessed data can be helpful since fetching from cache is faster compared to other methods.

I have not used Couchbase Server's AI capabilities yet. Currently, we are focused on storing and retrieving data faster with Couchbase Server, but I haven't had the chance to explore AI features.

I haven't utilized the AI capabilities of Couchbase Server, so I'm uncertain about its accuracy or reliability in output. However, Couchbase Server can handle billions of records, fetching them within milliseconds, but without firsthand experience in AI, I cannot provide thoughts on that aspect.

My advice for others considering Couchbase Server is to determine if the data is structured in JSON format, as it offers significantly improved facilities compared to others. I would rate this product an eight out of ten.

I use Couchbase Server as a main database to store information as key and value objects for geolocation-based lookups for place data. I use it for many purposes, depending on the use case. I use its indexing feature, its search feature, its querying feature, and everything depending on the type of project and complexity. Halalfoodle is a location information catalog for restaurants. I also have another use case for an ORTB system to keep analytical counters, not all the analytical data, but counters and configurations, because it is easy to set up and easy to manage with its beautiful UI, which saves me from needing extra UI tools. It saves me time.

I use Couchbase Server because it allows me to use it as flexible data storage. If I want, I can use it as key-value storage. If I want, I can use the SQL feature to query it. If I want, I can use its analytical views feature to create necessary views to query. I think its primary and greatest feature is the UI, which simplifies many things. With another database, you have to have a separate client utility from the terminal. This one gives you a UI which is beautiful and easy to use. It really saves time. The XDCR feature is the best. I simply set it up, define the IP address, and it automatically distributes the data between the data center instances, which is a very helpful feature. There is no headache, everything is out-of-the-box, and all of it is great.

Couchbase Server has definitely improved the workflow in my organization. The UI out-of-the-box does many things. I recently discovered collections and scopes, which I was not aware of, but after discovering them, they saved me many things related to governing indexes and creating special indexes to query. Now I can put data structures in the collections, which I can directly look up. I know that in a specific collection, I will get only specific types of documents, instead of having everything together in one place. That is great. After struggling with custom-based sequences and custom pointer documents that have numeric values pointing to the original document, now with collections and scopes, I can separate data structures, which saves me time. The UI is the best. All of these features have saved me maintenance costs and improved operation performance. I can quickly log into the UI and handle all the necessary operations. I can check logs and see warnings, everything in one place. I do not need extra items to use it.

Couchbase Server is very performant. I had a situation where I used it as session storage once in my lifetime, and it was very powerful. It handled DDoS situations when the application was creating 100,000 sessions in a second, and it was very fast.

It would be great to have a kind of pub/sub in Couchbase Server. I want to have a kind of stream in the UI to create a stream separately and have some metrics. By pushing the data to the stream, I could consume it on another side. Currently, I am using Redis or Redis-based applications. I use NATS from GoLang. I use Kafka and RabbitMQ. I need something out-of-the-box that is performant as Couchbase Server. It will save me time from having extra items to be installed. With Couchbase Server, everything is centralized, whatever I need, even to create triggers on some kind of collections when something changes, it triggers something, and I can immediately process it and do everything else.

Another thing I would require comes from CouchDB. In CouchDB, I was able to have multiple versions of the same document. It is like a document, and you have revisions of the document. In Couchbase Server, I know it is built upon CouchDB, and I see the metadata and other related elements, but I want to have the easiest way to see the versions of the document from the UI or from the client-side, just querying to show me revisions and just taking them by revision, rolling back, or whatever it is. I know everything is existing in the protocol and under the hood, but making such features easier to use and visible would be great. Pub/sub, or streams and data streams, and the ability to see the revisions of documents would be a great addition.

I have been using Couchbase Server since 2014.

Couchbase Server is stable enough in my experience.

I use XDCR in Couchbase Server to add servers and do the master replication. It works beautifully out-of-the-box.

I have not contacted customer support for Couchbase Server because I use the community version. I am on my own and do my own project. For some other components, I always use community-based versions. That is why I have not used support.

I previously used MongoDB and ArangoDB before choosing Couchbase Server. All of them are good. From knowing how Couchbase Server works and the performance outcome which I saw in real projects during battle testing and during anti-DDoS efforts, during my own project, I still keep using Couchbase Server and I am comfortable with it. I never think about switching to SQL-based servers. I do not think about switching to MongoDB and others. This is only the case if I am able to control the architecture.

It is easy to install with no problem.

That is the thing. I do not need DevOps or DBA database admins. Being a CTO of my own project, I simply installed Couchbase Server in multiple servers, configured XDCR, connected any of the server instances, and operated with them. It did everything related to automatically distributing the data out-of-the-box. I am currently building a client driver for the Crystal language stack, which is helping me to understand how Couchbase Server works under the hood by utilizing Memcached protocol and HTTP-based protocols. I am getting familiar with Couchbase Server, which makes me learn new things. By doing it, I am getting more excited about how it makes a developer's life simpler, and there is no need for an extra person to support it. I simply go, install, configure XDCR, check the logs, check necessary parameters, and everything is out-of-the-box. Nothing specially is needed. I even use the CLI tools for backing up and recovering. It is a time-saver. Everything I need is out-of-the-box. I do not know what else I could ask for. It impressed me. I am more than happy.

It is very opinionated because every other database is competing with each other and adding extra new features to be successful. That is why it is a bit hard to give some concrete opinion. My vision for this is if you are experienced enough and you need something flexible where you can enable and disable some features, by keeping key-value storage only or adding SQL++ feature, or adding views, or adding search features, or indexing, Couchbase Server is giving all flexibilities. You can always correctly define how to use memory and how to distribute computer servers' powers. I would give this product a rating of 8.

Couchbase Server is my main use case in a product-based company at Amdocs, specifically for an Amdocs billing product where Couchbase Server is the core backbone of our application, and I am using a multi-node cluster in a very large environment.

In my daily operations, we have our ordering services integrated into the billing product in the telecom sector, and in that service, we use Couchbase Server bucket as in scope and collection; thus, as part of our application flows, we frequently utilize Couchbase Server bucket with N1QL queries.

Couchbase Server is mainly used for the ordering services, supporting whatever the customer purchases and orders, making it the backbone of our software.

Couchbase Server is robust and has self-healing capabilities; whenever a failure happens, it performs failover and rebalancing, providing high availability and ease of use whether it is deployed on a single node or multi-node server, as well as in containers.

When a node failure happens in practice, Couchbase Server automatically performs failover, bringing the node back online, and then we can do rebalancing where all the VBuckets maintain an online state, ensuring end users are not impacted, and high availability is provided, as well as multiple disaster recovery setups for replication through XDCR to avoid service impact for our multiple services and maintaining query, data, and indexing services in my production environment.

Couchbase Server provides multiple services including event services and supports both JSON and non-JSON data formats, which is a significant aspect of Couchbase Server.

Since working with Couchbase Server starting from version 6, where only scopes and collections were available, I have seen numerous improvements with the release of version 7, especially as bugs identified in version 6 were addressed by the Couchbase Server team.

One specific outcome I have noticed is identifying constraints such as not being able to create more than thirty buckets, which we notified the Couchbase Server team about, along with several missing monitoring parameters; they worked with us to provide better solutions in terms of monitoring and the metrics we require for our production monitoring setups, ensuring our production is up and running smoothly.

Regarding improvements, I feel that the current dedicated monitoring, such as CMX offered by Couchbase Server, requires enhancements for better identification of issues, especially since the market is moving towards AI-driven solutions, and I believe Couchbase Server is working on improving its AI capabilities.

Couchbase Server requires more enhancement, particularly with the MCP launched by Couchbase Server which is not yet fully functional and offers limited tools that are not beneficial for automating production workflows.

Regarding the accuracy and reliability of Couchbase Server's AI capabilities, I perceive there are gaps since the tools are not being developed maturely and require more developed solutions for our agent workflows to facilitate automation with AI agents.

I have been using Couchbase Server for the last five and a half years in my day-to-day operations.

In terms of governance and security, I see Couchbase Server as highly secured, using SSL certificates and allowing for controlled user access without any noticeable gaps in security, though I do suggest vigilance as the AI-driven market develops.

Couchbase Server is currently deployed in both the public cloud and on-premises; in the public cloud, we have deployed it within Kubernetes, while on-premises, it is on a server level.

We are using AWS for our public cloud deployment.

We have indeed purchased Couchbase Server through the AWS Marketplace.

Monitoring and AI-driven enhancements are critical as the market transitions to AI.

I would advise others considering Couchbase Server to note that compared to other tools such as MongoDB, it is easier to use, reliable, and offers high availability while continually adding more features, making it a suitable choice, especially for large data environments.

I have shared all my thoughts regarding Couchbase Server, including its beneficial aspects and current limitations, and I believe a focus on these limitations will allow end users to take full advantage of the product. I would rate this product a seven out of ten.

Couchbase Server serves as the primary use case for our real-time web and mobile application backend with caching. We utilize Couchbase Server for microservice session isolation in our Java Spring Boot backend, leveraging Couchbase CrudRepository to instantly save and retrieve complex JSON user profiles. Couchbase Server's memory-first architecture handles our high-volume read-write workloads incredibly fast.

We use Couchbase Server to manage user sessions, a dynamic product catalog, and real-time telecom-style insights where microsecond data persistence and sub-millisecond query response are strictly required.

One of the best features that Couchbase Server offers is scalability due to Multi-Dimensional Scaling. Unlike other NoSQL databases where every node has to run every service, this MDS allows us to scale services independently.

Multi-Dimensional Scaling has helped our team by making scaling easier in a noticeable way. If our data volume grows, we scale the data service. If we are running heavy lookups, we horizontally scale just the index or query services.

Couchbase Server has positively impacted our organization by successfully eliminating our data layer silo issues. Instead of stitching together a separate database, a separate caching tier, and a text search platform, Couchbase Server handles operational data, indexing, and vector searching inside one unified data platform. This saved our infrastructure team immense maintenance overhead.

The administrative dashboard web UI of Couchbase Server could benefit from more interactive visual mapping tools for complex, multi-document transactional tracking, which would help in simplifying the debugging option for newer database administrators.

I have been using Couchbase Server for about three years to manage high throughput, low latency NoSQL data layers for our production systems.

Couchbase Server is an absolute powerhouse for high-velocity modern enterprise applications and bridges the gap between flexible schema advantages of NoSQL and the rigid, trusted query capabilities of relational databases beautifully.

I would recommend taking full advantage of Multi-Dimensional Scaling during the initial infrastructure sizing. Isolate the query, index, and the data workload into a separate node. This ensures your heavy operational reads and writes never choke your search indexes, maximizing your cluster performance from day one.

We run Couchbase Server in a hybrid multi-cloud architecture. We use Couchbase Server on our private, on-premises servers for sensitive data compliance, but we also run it inside our public cloud environments on Amazon EC2 instances. This allows us to sync data effortlessly from our localized database up to the public cloud using Couchbase Autonomous Operator for Kubernetes.

I purchased Couchbase Server through the AWS Marketplace. I would rate this product a nine out of ten.

Couchbase Server is used primarily for caching to store values, which provides the software with increased speed and helps find and certify that values are correct on the server.

In the software, we have employers and sellers. I use Couchbase Server for the configuration of sellers, including money and POS, which is a small terminal. The seller is certified to draw. We have between 5,000 and 10,000 sellers in the database. Couchbase Server is used to cache the configuration values for any seller in the software.

Couchbase Server provides us with more flexibility and a great cache. It provides speed for the software and is the main component for speed.

When our sellers are certified in the streets, the terminal does not get information from the relational database. Instead, it finds the configurations in Couchbase Server for more speed in the operation.

The best feature is the query in Couchbase Server to search configurations using SQL.

When I need to search for a specific value, I use SQL to find it. SQL is the main feature I use in the company.

The improvement is more speed. Speed is the main improvement my company has experienced with Couchbase Server.

The main use is caching the values.

I have worked in my current field for more or less ten years. I have worked with Couchbase Server for between five and seven years.

Couchbase Server is very stable.

I have not used the AI capabilities in Couchbase Server. I cannot respond about these capabilities in Couchbase Server because I am not in the group that deals with governance.

I am very satisfied with Couchbase Server. Our senior developers consult the documentation.

Perhaps Redis for its key-value storage, but I am not interested in changing from Couchbase Server to Redis now.

We use one server.

Time saved.

Perhaps.

The advice is that you will gain software speed. Use Couchbase Server to make your software more scalable. The interview is very good, with questions that are very direct about the product, Couchbase Server.

I would rate Couchbase Server a ten. I have been using Couchbase Server for ten years, and it is comfortable to use. I gave this review a rating of ten.

I used Couchbase Server at ViajaNet five years ago, and I am currently using it at Vertiv for cache specification.

I primarily use Couchbase Server for cache because this cache is very useful and the performance is excellent. I need ultra-performance for risk analysis. In my order flow, I need to obtain more information about the participant and the count of the order that exists, and I require precise information with ultra-performance.

In the order flow, if a participant makes three orders in two seconds, one second, or one minute, it is accounted for, and I have rules for specific times when this participant makes orders.

Couchbase Server is important for performing in several flows that I have in my company.

The best feature Couchbase Server offers is performance.

When I say performance, I mean the way Couchbase Server structures and manages data. I specifically appreciate the performance that Couchbase Server provides.

Couchbase Server has positively impacted my organization, as it is important for the maintenance and security of the flows I have noticed.

Couchbase Server should improve performance and make the process scalable. The integrity of the information is improved by it.

I have been working as a software engineer in my current field.

I feel there is nothing I should improve, and I do not think about improving anything. I did not purchase Couchbase Server through the AWS Marketplace. I do not have advice for others looking into using Couchbase Server. I would rate this product a 10.