Couchbase vs MariaDB Platform

• 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

Read full review

• Simpler learning curve. MariaDB is a cleaner, simpler system that is (IMO) easier to learn and easier to manage effectively than many other database systems.
• Lower hardware requirements. After migrating to MariaDB from another database software system, we find that our hardware needs have substantially decreased.
• MariaDB support is very responsive. It's like they actually care. On the few occasions we've run into technical issues, support has always come through with what we needed. Once it was showing me a relatively new feature the server supported that I wasn't aware of, that, once I was able to properly make use of it helped me resolve a serious production performance issue.
• Architectural flexibility. As an example, the ready availability of synchronous (Galera) versus asynchronous replication schemes without being locked into one of the other by enormous technical complexity or punitive licensing, allows the customer to find what really works best for their needs.

Read full review

• 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.

Read full review

• Driver Support - Some third party applications use database drivers that cause unexplained slowness with MariaDB. This can be worked around by using the MySQL drivers, but it's not clear what causes the problem in the first place.
• Support - While online communities are helpful in diagnosing problems, there isn't as much professional documentation/support available for MariaDB as some of the other major database options.
• Data Visualization - It would be helpful if there were more built in options for analyzing statistics and generating reports.

Read full review

• 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.

Read full review

• Low CAPEX if you have a team that use open source software day by day
• Medium OPEX if you have a team that use open source software day by day
• Perfect to use in academic ambient to support researchers and students

Read full review