Azure Cosmos DB vs. Couchbase Server

NoSQL platforms are very useful when it comes to security, speed, accuracy, high accessibility with high read and write power. Everything is managed under the cloud and we have the various capabilities of Azure and support for Microsoft products with us. Flexibility in price and variety of features, as well as real-time results, are some of the popular [features] of this platform.

Incentivized

Best suited when edge devices have interrupted internet connection. And Couchbase provides reliable data transfer. If used for attachment Couchbase has a very poor offering. A hard limit of 20 MB is not okay. They have the best conflict resolution but not so great query language on Couchbase lite.

Incentivized

• Turn-key geo-redundancy with multi-master writes is unprecedented and unparalleled in the industry!
• Guaranteed low latency makes Cosmos DB an excellent fit for most of our performance-intensive situations.
• The tunable consistency model simplifies so many challenges in distributed systems engineering that otherwise require advanced knowledge of computer science topics. I continue to be impressed at how Cosmos DB has abstracted away so much complexity.

Incentivized

• Easy to store unstructured data and has great performance
• Managing security is super easy which can be managed across different levels
• UI is pretty simple to use and manage the cluster
• Backup of the data is very easy and the restoration/recovery is fairly easy as well with the in-built tools.
• Easy integration with elasticsearch for replication
• It is fairly easy to scale up or scale down the cluster

Incentivized

• When searching by default, it is case sensitive, which must be changed by default
• In many ways, the price should be more flexible according to the requested facilities, because the price is very expensive for startup companies.
• It is not fully compatible with most common Streaming Analytics tools applications and developers should be worked on it

Incentivized

• Cluster sizing during the design phase can be improved, especially if the client lacks prior experience. Vendor consultants are very meticulous in order to provide best of class performance and response time, although some more real-world pragmatic approach is often needed.
• Couchbase Lite 2 went thru a major revamp, which broke the compatibility of the applications with some features removed and other changed. That needed development teams working to refactor the applications.

Incentivized

It's efficient, easy to scale, and works. We do have to do a bit of administration, but less now than when we started with this a couple of years ago. Microsoft continues to improve its self-management capability.

Incentivized

I rarely actually use Couchbase Server, I just stay up-to-date with the features that it provides. However, when the need arises for a NoSQL datastore, then I will strongly consider it as an option

Incentivized

Like I said, Cosmos is the way to go. From all of the services that Azure has, Cosmos is very robust in terms of usability. It's ever-evolving and integrates with other applications seamlessly. The interface is pretty easy to understand. I implemented various solutions for my company and Cosmos was one of them.

Incentivized

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.

When we are Live for more than 6 months, I'm hoping to enhance this rating.

One of Couchbase’s greatest assets is its performance with large datasets. Properly set up with well-sized clusters, it is also highly reliable and scalable. User management could be better though, and security often feels like an afterthought. Couchbase has improved tremendously since we started using it, so I am sure that these issues will be ironed out.

Incentivized

The support team is very responsive and we are generally satisfied with Microsoft support, in my opinion support team of a product and service is just as valuable as its quality and performance. Telephone answering, 24-hour hotline, email support and ticketing are excellent.

Incentivized

I haven't had many opportunities to request support, I will look forward to better the rating. We have technical development and integration team who reach out directly to TAM at Couchbase.

Azure Cosmos DB for MongoDB is more affordable than many other solutions and works incredibly well if you're within the Azure ecosystem.

Incentivized

Couchbase could outperform it's competition considerably for database reads and writes. Full text searches were still faster in Elasticsearch but this is more of a feature than a base platform requirement for us.

Incentivized

So far, the way that we mange and upgrade our clusters has be very smooth. It works like a dream when we use it in concert with AWS and their EC2 machines. Having access to powerful instances along side the Couchbase interface is amazing and allows us to do rebalances or maintenance without a worry

Incentivized

• Expensive but works if your infra is on Azure data center.
• No latency and nearly no downtime.
• Takes time for end users to adapt.

Incentivized

• There have been several areas of our application [that] really needed an ACID compliant database (e.g. strong transactional guarantees) that we thought we could work around while using Couchbase. [In my opinion] that turned out to be a poor bet. You need to be certain that the specific characteristics of a NoSQL database fit your problem.
• Couchbase does eliminate the need for schema upgrades completely. I.e no downtime or conversion windows as you migrate your data model, adding attributes, etc. This helped with the deployment timeframe associated with DB changes.
• The database is (apparently) a bit more of a space/memory consumer than originally anticipated. During deployments, we received constant pressure from Couchbase consulting teams to eliminate/reduce the number of indexes, and this was because any mutations to docs in a bucket must check for impact against all indexes. More recent years have started to address this with their "collections" features, which helps isolate indexes to specific sub-groupings of documents.

Incentivized