When comparing CockroachDB vs MySQL with InnoDB, the Slant community recommends MySQL with InnoDB for most people. In the question“What are the best ACID-compliant scalable databases?” MySQL with InnoDB is ranked 3rd while CockroachDB is ranked 9th. The most important reason people chose MySQL with InnoDB is:
Some of these APIs include ODBC, Java (JDBC), Perl, Python, PHP, Ruby, and native C. Also, there are a number of third party APIs that are available for use to interact with the database
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro High availability
Pro Distributed transactions
Pro Automated scaling & repair
Pro Cross Cloud Provider Replication/Migration
Run CockroachDB nodes in two or more cloud networks (AWS, GCP, Azure) and replicate the databases. Migrate from one cloud provider to another.
See this blog article for details: https://www.cockroachlabs.com/blog/cross-cloud-migration/
Pro SQL
Pro Strong consistency
Pro Simplified deployment
Pro Multiple APIs
Some of these APIs include ODBC, Java (JDBC), Perl, Python, PHP, Ruby, and native C. Also, there are a number of third party APIs that are available for use to interact with the database
Pro Many applications available
There are a number of applications that are built with the focus of MySQL. Some of these include Drupal, Joomla, Wordpress and more.
Pro Scalable
Works well under simple operations or heavy tasks.
Pro Huge community support
Being the world's most popular open source database means there are tons of available examples and information for users' to access.
Cons
Con Immature project
Some important features are missing and heavy use in production is minimal.
Con InnoDB is not fully configured
When you initially install MySQL, InnoDB needs to be configured to make it suite your needs and there are many issues you can come across.