It was a tremendous experience
What do you like best about the product?
The most liked attemt to stay connect with Couchbase is the ease of work station. It is effortless to use.
What do you dislike about the product?
Anything related to Couchbase is enough to attact data scientist where stability is better with time management of index building.
What problems is the product solving and how is that benefiting you?
Couchbase easily retrive all the require data I need from my document database with high range of scalability.
Smooth and well documented
What do you like best about the product?
Documentation is well explained on Couchbase official documentations.
What do you dislike about the product?
Not very popular yet, difficult to build a case to use couchbase
What problems is the product solving and how is that benefiting you?
We were using it for our database of an application we were using - good NoSql soln
High performance NoSQL database with multi-model support and distributed scaling.
What do you like best about the product?
It's flexible to support diverse use-cases, distributed scaling with json native feature, supporting modern application development.
What do you dislike about the product?
Cluster management, data validation and governance are the downsides of couchbase.
What problems is the product solving and how is that benefiting you?
I used it for document AI needs, to extract intelligent candidates from the unstructured data powered by AI system and stored the results as kv pairs, integrated with enterprise apps to enable the business workflows.
Ease to use
What do you like best about the product?
The best thing I like about the couchbase is the it's ease of use. I've been using the artifical intelligence services created by couchbase using GenAI for my daily coding activity and it really comes in handy!
What do you dislike about the product?
While couchbase offer various features, but its intial setup and configuration can be challenging for a new user. Additionally, while the document is very well documented however lacks clarity in certain areas and making troubleshooting.
What problems is the product solving and how is that benefiting you?
Couchbase addresses several key issues related to data management and application performance. Primarily, it solves the challenge of handling high-speed transactions and large-scale data processing. By using Couchbase, I benefit from its high availability and low latency, which are crucial for real-time applications. The platform’s ability to efficiently manage large volumes of data and provide quick access through its key-value store improves the overall responsiveness and reliability of applications. Furthermore, the ease of scaling Couchbase horizontally means that as data grows, performance remains consistent, ensuring a smooth user experience. This scalability and efficiency ultimately lead to better resource utilization and reduced operational costs.
couchbase
What do you like best about the product?
Easy to manage, scale the DB's
higer availablity with multiple nodes can serve the traffic.
What do you dislike about the product?
when two or more hosts go down in larger data DB's then we seen trouble in accessing the data.
What problems is the product solving and how is that benefiting you?
retriving is very fast when compared to RDBMS
Scalability is easy..
less downtime for upgrading
An easily scalable document data store
What do you like best about the product?
It is easy to scale a Couchbase cluster by adding a new node and rebalancing the cluster.
What do you dislike about the product?
There are at times connection issues or query timeouts which are not so straightforward to resolve.
What problems is the product solving and how is that benefiting you?
Being a document data store, the schema is flexible and it is easy to store different types of data in a couchbase collection.
Very intuitive and great experience
What do you like best about the product?
Easy to use, and documentation easy to understand
What do you dislike about the product?
Long documentation in order to understand one topic
What problems is the product solving and how is that benefiting you?
host databeses in the cloud
A breeze to work with
What do you like best about the product?
Couchbase work like a charm and integrates easily with my existing tech stack. As an agency i can use it for clients work very fast with less headache
What do you dislike about the product?
I would really enjoy having a subscription plan also
What problems is the product solving and how is that benefiting you?
Usually providers offer either sql or nosql. finding a place with sql capability and document database is very interesting to me
Couchbase is an excellent NoSQL database having the on-premise version as Couchbase server and the cloud version as Capella.
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
Easy querying language.
Easy to increase server capacity as per usage demand.
Easy UI interface.
Data storage is easy and we do not have to navigate different tables for extracting relational data.
Time to extract the data is faster than non-relational databases and hence there are fewer performance issues.
What needs improvement?
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.
For how long have I used the solution?
I have been using it for one year.
What do I think about the scalability of the solution?
For Couchbase server, nodes have to be created or reduced based on requirements, which is a technically complex task.
For Couchbase Capella, there are different combinations CPU and Memory available which can be configured as per requirements and hence it is more flexible.
How are customer service and support?
Couchbase could also improve with their technical support and provide project specific solutions rather than generic.
How would you rate customer service and support?
What other advice do I have?
Couchbase is a good NoSQL server and I would recommend it to users, simply because if the simple way of storing the data (in the form of JSON) as well the easy process to retrieve it.
Customer support is good and they will help you in suggesting mitigation measures for most of the issues being faced by the project.
There is no major knowledge gap while transitioning to a non-relational database, knowledge of SQL querying and JSOn models are sufficient.
Overall, I would rate it an eight out of ten.
Couchbase microservices for Amadeus (hotel software company)
What do you like best about the product?
I really liked how simple it is, how easy it can be dockerized and above all the document management that a good infrastructure allows.
What do you dislike about the product?
There is not much documentation for nodeJS, the orm is poorly documented and there are no very current versions to use it in the most recent versions of nodeJS
What problems is the product solving and how is that benefiting you?
unification of other services in a single document that allows sharing with other subsystems within the app
