Couchbase Server
Couchbase | 7.6.3Linux/Unix, Amazon Linux Amazon Linux 2 2.0.20200904.0 Update - 64-bit Amazon Machine Image (AMI)
External reviews
131 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Blasing fast performance but difficult to operate at scale
What do you like best about the product?
- KV Lookups Performance
- Support for nested document JSON operations
- Comprehensive Web console with useful metrics
- Support for nested document JSON operations
- Comprehensive Web console with useful metrics
What do you dislike about the product?
- Frequent breaking changes on the SDK
- Server upgrades often lead to downtime as the client needs to reconnect
- .NET is poorly served in general, the documentation should be improved
- Server upgrades often lead to downtime as the client needs to reconnect
- .NET is poorly served in general, the documentation should be improved
What problems is the product solving and how is that benefiting you?
- Fast lookups for risk rules to be evaluated as part of a payment processing workflow
- Indexing of risk rules
- Velocity computation for risk features
- Indexing of risk rules
- Velocity computation for risk features
High performance, high reliability
What do you like best about the product?
It's super performant and very reliable. There is a DCP (database change protocol) which can be used to react to mutations. This is very useful for any streaming use cases including integrations
What do you dislike about the product?
No materialised views. No out of the box odbc or jdbc connectors. You have to buy these from 3rd party vendors at high prices.
What problems is the product solving and how is that benefiting you?
We use it for a wide range of operational systems which serve front end and back end applications. There is no tolerance for lost data and we read and write at massive scale. We persist everything to disk and maintain around 90% of keys in memory for fast access.
Recommendations to others considering the product:
Look at the analytics and eventing modules. They are very powerful
Decent Database for JSON data
What do you like best about the product?
It is very simple and has no complex configuration. It stores data in different buckets, similar to tables in RDBMS. It provides bucket to bucket sync or cluster level to diff cluster level sync using XDCR, which helps in syncing or moving data. As it saves data in JSON format, it's really easy to structure data in couchbase. It works on the N1ql query and provides suggestions for index too.
What do you dislike about the product?
I dislike, its response time, we faced lots of issues in reducing the query time, even though we have created all the necessary indexes, still, the response time was high. Another thing where we faced an issue was in eventing functionality, as the proper log is not displayed on UI, it's difficult to understand for which document the eventing worked or not.
What problems is the product solving and how is that benefiting you?
We have built a consumer app, where users create documents, which we save in couchbase DB, and further, read it back when requires. It helped us in creating the app quickly, as it is very easy to start working on couchbase. They also provide a cloud version of couchbase, which is easy to configure.
Real NoSQL database
What do you like best about the product?
Web console GUI is great to use and it's XDCR distributed architecture allow you to store/access data geographically.
What do you dislike about the product?
As far I used, all the available features are good.
What problems is the product solving and how is that benefiting you?
As of now no issues.
Recommendations to others considering the product:
Nil
There are certain key features that I found more optimum for what Mount Sinai can take advantage of.
What do you like best about the product?
The integration and isolation of workload features are the best.
What do you dislike about the product?
Not sure yet. Need to try more to see if there are any features that I may dislike or find common.
What problems is the product solving and how is that benefiting you?
Primarily integration issues and managing multiple workloads and having a distributed team.
Couchbase for everyone
What do you like best about the product?
Query lang N1QL is convinient, detailed and very fast.
Faster key-value storage.
Integration with other platforms viz Elasticsearch.
Scalable across multiple locations.
Couchbase has been quite a usable for our implementation. We had similar experience with our previous "trial" implementation, however it was short lived.
Couchbase has so far exceeded expectation. Our implementation team is more confident than ever before.
Faster key-value storage.
Integration with other platforms viz Elasticsearch.
Scalable across multiple locations.
Couchbase has been quite a usable for our implementation. We had similar experience with our previous "trial" implementation, however it was short lived.
Couchbase has so far exceeded expectation. Our implementation team is more confident than ever before.
What do you dislike about the product?
We're still evaluating the business outcome, so far we are observing inconsistent resource utilization (viz memory, cpu), may be we need to optimize further.
What problems is the product solving and how is that benefiting you?
We wanted a multi-region multi-cloud Infra statistics storage platform for Analytics and Decision making. So far it has solved the purpose of multi-region multi-cloud Infra statistics storage.
We're using couchbase to gather Infra health, stats for near real time analytics, to make decisions to scale out or up the Infra.
We have more than 40K servers in our Infra, both virtual and physical. We've historically had slow processes, to reading performance statistics from each of them and analyzing them. Before we could react to a need for server upscale, an incident would have happened. This is where we tried other solutions and are currently using Couchbase. We are able to load vast amount of data every second and come up with near real time decisions.
We're using couchbase to gather Infra health, stats for near real time analytics, to make decisions to scale out or up the Infra.
We have more than 40K servers in our Infra, both virtual and physical. We've historically had slow processes, to reading performance statistics from each of them and analyzing them. Before we could react to a need for server upscale, an incident would have happened. This is where we tried other solutions and are currently using Couchbase. We are able to load vast amount of data every second and come up with near real time decisions.
Recommendations to others considering the product:
My recommendation would be for scenarios with real time analysis where we are satisfied. I'm not yet able to provide recommendation to scenarios which involve real time processing, I'm also less knowledgeable here.
It is really good. Easy to learn
What do you like best about the product?
Best NOSQL db to use. Easy to learn. Especially document creation.
What do you dislike about the product?
We cannot replicate large db in couchbase
What problems is the product solving and how is that benefiting you?
It can be integrated with any technology.
Recommendations to others considering the product:
We cannot implement logic in couchbase. Should be handled in code.
Cool Tool
What do you like best about the product?
I really love the N1QL module, which allows you to use SQL like syntax to work with documents.
What do you dislike about the product?
Can't say I dislike it, but I'd like for better docker support, since right now it's a bit difficult to automate the setup of a docker container. I'd also like to see an in memory version of couchbase to use for testing.
What problems is the product solving and how is that benefiting you?
I used couchbase for geolocation queries as well as a standard database.
I just read about it.
What do you like best about the product?
Good is uptime and speed. And mainy nosql.
What do you dislike about the product?
No as such, i if its give SQL support if needed then its better.
What problems is the product solving and how is that benefiting you?
I am working on simple invoice app, that's the schema less structure which i am able to achieve.
Educational and Research
What do you like best about the product?
Document key value and N1QL usage with the Firebase .
What do you dislike about the product?
Document does not update automatically after query.
What problems is the product solving and how is that benefiting you?
Integration of queries with firebase
showing 21 - 30