Couchbase Reviews

We use it for data link utilization.

The horizontal scale is a major factor. We want to be able to expand our capacity horizontally.

The failover and failback could be a bit easier. When I looked at it last time, it had to be manually done. It also took over an hour for us to rebalance all the nodes.

It's pretty stable. We like it.

Scalability could be a bit more desirable. We are probably a little hardware limited.

With AWS, it might be better. We're also looking at DynamoDB as a possible replacement.

We also looked at MongoDB, some sort of eMemory, and cache layered with a traditional relational database for performance sake, because we churn a lot of data. We collect for each customer upwards of around 20GB/hour of data. Therefore, performance is important to us, so NoSQL eventually became the obvious choice.

The decision was between this solution and MongoDB. We chose this because it came with N1QL, which is their query language. Whereas MongoDB, at that time, did not come with any sort of query capability.

Couchbase is a good solution to a lot of problems, but you will have to do your own research on it. It does have the scalability. It fits most of our needs. Though, the performance could be quicker and better, especially in the querying process.

We actually have not used it with AWS. We just purchased directly with them, and we have our own hardware. As part of our solution, we are now looking to move some of the solution to AWS. We want to provide solutions to our customers and package it as a product, and it feels like a lot of people are asking for cloud as an option. Therefore, we are looking into cloud deployments instead of on-premise deployments.