Amazon DocumentDB (with MongoDB compatibility) vs. Couchbase Server

AWS Document DB (with MongoDB compatibility) is well suited when for all the workloads due to its huge feature offerings which will reduce our operational overhead and due to that we can focus more on our WorkLoad rather than optimising and fine tuning Databases. Its Offerings are Advanced Monitoring, DB cluster Upgrades, Migration Assistant, High Availability, Fault Tolerance, Data Durability, Security, Storage Auto Scaling, Backup Restore policies.AWS Document DB (with MongoDB compatibility) some of the features that are there in some other services like MongoDB Atlas that offers vast amount of features plus Supports Multi Cloud while Deploying Database clusters, Immediate support to latest Mongo DB versions, Mobile & Edge Sync like Atlas Edge Sync, Freedom to choose Database deployment in Any top Public Cloud, Having more then 100 plus Monitoring and Telemetry metrics for index and schema recommendations, More Compatibility with MongoDB queries.

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

• Amazon DocumentDB (with MongoDB compatibility) provides Auto scaling of cluster as a by default functionality through this we can focus on more on our applications end
• Through AWS Document DB without much operation overhead we can configure for Database's high availability, Durability, Backup Restores policies, Advanced Monitoring, Security Parameters.
• Also they can provide us a Guide for Database Migration from any Supported Mongo DB vendor to AWS Document DB.
• Via AWS Document DB query Logging ( Profiling ) we can fine tune our database queries and hence improving our END to END Customer Experience and Product Enhancements.

Incentivized

• Couchbase performance is exceptional both for in-memory and persisted transactions.
• Handling of node failures and cluster rebalancing (high availability).
• Enterprise support from Couchbase themselves
• Good documentation
• Streaming of bucket (database) level mutations via their Database Change Protocol (DCP).
• Replication of datasets between native clients and Couchbase buckets
• Handling of simultaneous writes to the same record with performance penalties

Incentivized

• Give support for Latest Mongo DB versions available in market
• AWS Document DB is limited up to 32 shards per cluster and 2 shards per Document DB instance and all within single region
• Start supporting more numbers of Rich data types
• Should have access to MongoDB experts who throw light on Cutting edge mongoDB features and integration consulting.

Incentivized

• The N1QL engine performs poorly compared to SQL engines due to the number of interactions needed, so if your use case involves the need for a lot of SQL-like query activity as opposed to the direct fetch of data in the form of a key/value map you may want to consider a RDBMS that has support for json data types so that you can more easily mix the use of relational and non-relational approaches to data access.
• You have to be careful when using multiple capabilities (e.g. transactions with Sync Gateway) as you will typically run into problems where one technology may not operate correctly in combination with another.
• There are quality problems with some newly released features, so be careful with being an early adopter unless you really need the capability. We somewhat desperately adopted the use of transactions, but went through multiple bughunt cycles with Couchbase working the kinks out.

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

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

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.

The Apache Cassandra was one type of product used in our company for a couple of use-cases. The Aerospike is something we [analyzed] not so long time ago as an interesting alternative, due to its performance characteristics. The Oracle Coherence was and is still being used for [the] distributed caching use-case, but it will be replaced eventually by Couchbase. Though each of these products [has] its own strengths and weaknesses, we prefer sticking to Couchbase because of [the] experience we have with this product and because it is cost-effective for our organization.

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

• Great Customer Experience as DB queries are fine tuned
• Less Operational Overhead to manage and take care of the Database
• Automatic applying of Small patches

Incentivized

• Great performance.
• Leading Couchbase Lite capabilities for mobile use.
• Developers' learning curve with replica reads and multi cluster can be long. Needs guidance and nurturing.
• Cluster maintenance during OS patching, etc. has multiple ways to approach. Operational teams may need some guidance.

Incentivized