Couchbase vs MySQL

• 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

• The Community Server edition remains a strong candidate for a SQL-based database solution that supports a wide array of data structures.
• It scales well for both small business and enterprise use.
• It performs very well provided your database schema is well-planned and carefully considered (which is the case for any database solution).
• It has a number of interface solutions including GUI-based ones such as phpMyAdmin and MySQL Workbench that allow for easy management of your databases.

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

• MySQL doesn't provide good data wrangling functionalities, such as parsing JSON or XML. We had to transform them outside MySQL on the web application server side using JSP.
• As we move forward to adopt more genomics information, MySQL may lack of dealing with "big data" functionalities.
• It is a freely available S/W and easy to manage budget, but there are possibilities to spend cost for additional technical support.

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

• Since MySQL is a free database package, if you have someone on staff that understands databases and how to use them, the ROI is very high when using MySQL.
• If you need to hire a MySQL developer to implement and manage your database then it can be quite costly to manage and that will negatively impact your ROI when using this product.
• Since there are some very expensive alternatives in the SQL database space, if you compare the overall costs of using MySQL to those other products, I think you will find your ROI is always better when using MySQL

Read full review