Try our new research platform with insights from 80,000+ expert users

CockroachDB vs MySQL comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

CockroachDB
Ranking in Relational Databases Tools
11th
Average Rating
8.0
Reviews Sentiment
7.7
Number of Reviews
12
Ranking in other categories
No ranking in other categories
MySQL
Ranking in Relational Databases Tools
3rd
Average Rating
8.2
Reviews Sentiment
7.5
Number of Reviews
147
Ranking in other categories
Open Source Databases (1st)
 

Mindshare comparison

As of December 2024, in the Relational Databases Tools category, the mindshare of CockroachDB is 3.1%, up from 2.3% compared to the previous year. The mindshare of MySQL is 8.3%, down from 9.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Relational Databases Tools
 

Featured Reviews

Antonio Tringali - PeerSpot reviewer
Open source with extensive documentation and a University for training
I am a freelancer. A client of mine wanted a solution that would allow them to scale yet not abandon the familiar PostgreSQL front-end (and rewrite a part of their source code). Scalability aside, CockroachDB is a fine way forward from PostgreSQL and is not changing the client source code part of the system. If you are lucky and you do not use newer features from recent versions of PostgreSQL or PostgreSQL extensions, it's fine. There are nice-to-have features for big organizations like regional tables. At the moment, my client simply does not use these. However, the serverless offer from CockroachDB is reacting well as data grows.
Patryk Golabek - PeerSpot reviewer
Good beginner base but it should have better support for backups
As for what can be improved, right now we don't use the MySQL cluster. There is a MySQL cluster that you can run in a standalone mode, like a single database or you can do it in a cluster master-slave implementation. The cluster is not the best when it comes to MySQL. That's why we switched to MariaDB. For that simple reason that the cluster there is better. It's more manageable and it's easier to work with. We decide what to use depending on the needs. For example, if we need to mount something in a cluster mode, we use MariaDB, which again, is a Dockerized solution with a Helm chart as well, and it's very easy for us to deploy and manage, and also to scale when you just increase the number of slave versions. So MySQL doesn't have that great support when it comes to clusters. You can definitely use MySQL for that too, both support clustering, but the MariaDB is better. Additional features that I would like to see included in the next release of this solution include better support for backups. Because if you go with the MySQL Percona version, it gives you the tools to back it up securely. The vanilla version of MySQL doesn't have that. It actually does have it, but it is just really poorly executed. I would improve the backup system as well as the encryption. To make it smoother right now takes too much work. It should be a little bit smoother to backup the encrypted data the way you want it and have the ability to push it anywhere you want. That is not part of it right now. Now it is a database, so you don't know what you're going to do with it. It's difficult. You're just going to come up with solutions. But I think you can generalize here and come up with really simple solutions, which we have already in MySQL. That's probably the one thing that I would try and push right now for people to switch. But people are still not biting, because if you go with the managed version, then all the backups are taken care of for you by Amazon or Google or Microsoft. Then you really don't care. But for us, since we're doing it locally, self-hosted, we would like to have better tools for locking up the data. Right now, one aspect that is also linked to backups is running things in a crosscheck with semi-managed solutions. This requires a bit of a context. Since we're running things within the clustered communities, we're kind of pushing the Cloud into the cluster. We also want to push some of the tools for the database into a cluster, as well. So these are what we call Kubernetes operators. And there's MySQL operators that were first developed by the community. Those kind give you the ability to backup data within the cluster. So now you have a fully managed solution running from your cluster. These are called MySQL Kubernetes operators. We are looking into those right now to upgrade our solution, which would mean that we can just execute our backup natively within Kubernetes, not via special scripts. This would make it much easier to actually deal with any kind of MySQL issues within the cluster, because it would be cluster-native. That's what the operators are for. I think Oracle just created a really good one. It surprised me that they have this. It's not because of Oracle, but they got pushed by the community and actually created the MySQL Operator for Kubernetes, and that's what we're moving towards. This is going to give you an ability to have a cloud-managed solution within the cluster. And then you can ask the MySQL Operator for the database. They'll partition the database and give it to you. So it will change the nature from you deploying it to you just asking the cluster to give you a database. It's a fully managed solution right from the cluster. So that's what we're heavily looking into right now. We'll be switching to using Kubernetes MySQL Operators. It's a high-availability cluster running within the Kubernetes cluster. Right now we're pretty good with that. It's working fine. We're trying to find some time to actually release that globally everywhere. That's where I am right now. But in terms of technology, if you give up Oracle, you just go to a MySQL operator. That's the one we're using, what we're actually looking at - to create, operate and scale mySQL and sell it within the cluster. This idea of having a cognitive MySQL becomes much easier to manage within the cluster, as well. So you don't have to go with the cloud solution with AWS or Google cloud or Amazon MySQL or the Microsoft version. The Oracle SuperCluster is the Oracle MySQL operator. That's what we we are looking into a lot right now. Mainly because it does backups on demand - it's so easy to backup. You can just tell Kubernetes to backup and you don't have to run special scripts or special extra software or codes to back it up. You can make the backup as you would do anything else. Send a backup or some other data source or insert an Elasticsearch into it here. Just say "Kubernetes, back it up" and you know Oracle has this adapters within the cluster to back it up for you taking increments or different companies. So that makes it really nice and easy to use and to deploy. With that kind of solution you can ask to class or petition the database how you want. So again, it changed the nature of the kind of push-to-pull second nature system. Are you pushing your containers to a cluster? You just say cluster, "give me a database" and the class gives you the base partition database, creates a database in a secure manner, gives the connection to the database, and you're done. Then you can back it up on a schedule on to any backup switches. It's much easier. So once this goes, it is going to be widely adopted, which it should be. But I think people might not have the tech skills right now. But once it's adaptive, maybe in a few more months, it's going to be the number one solution for everybody. In terms of what I'd like to see in the next release, one thing that's always missing is dash boarding. There's no real BI tool for MySQL, like there is in Yellowfin and all the different tools that you get. They all have MySQL connectors, but there's no specific BI tool for MySQL. Open source projects have sprung up, but they're more general purpose, like Postgress, a MySQL kind of database, a relational database. I don't see any really nice tool like Cabana for elastic searches that I can tell clients to use because it would be too technical for them. They would have to have more technical engagement with writing the course, drag and drop, and creating a graph like in Power BI where you just connect with DIA. So I'd like to see the grab and drag and drop tables, nice beautiful graphics, and pie charts. You don't necessarily have that with MySQL like you have other solutions, which are really cost prohibitive for some clients. It'd be nice to have an open source solution for that. Decent solutions. I mean decent that I can take to clients. It's so technical. They want to drag and drop.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The initial setup and deployment are simple."
"The most valuable features of the solution are its resiliency features and the geo-partitioning capabilities."
"The best feature of CockroachDB is the ability to keep the nodes in different locations."
"The subset of SQL that my client is using is completely supported."
"What I like best is its ability to solve data residency issues. The main advantage is auto geo partitioning, built into the product. This means we don't have to spin up separate servers in each region, which would be much more costly."
"The product has valuable security features."
"CockroachDB is highly reliable."
"The availability and the easy to use feature is the most valuable. The documentation is also good."
"It has a lot of features. The RDBMS, consistency, and multi-user features are valuable."
"It was easy to install."
"It is easy to use."
"MySQL gives us a very user-friendly workspace in which to query the database."
"It is a very stable solution. I deployed the product six years ago, and it still works fine."
"A good traditional database that supports JSON."
"MySQL's most significant attribute is its capability to create, modify, and maintain databases. This is crucial and advantageous in procedures, such as SOAR. Therefore, all SQL functions are beneficial to any backend developer or developer who requires data storage."
"Support for enterprise-grade features like clustering, master-slave replication, even Sharding (to some extent) which is an advanced feature."
 

Cons

"I think the engine itself could be improved. If you miss a partition key, it should be able to be modeled. This is where AI could be really helpful. For example, if a user is from Australia, the system should know to look for their data there first instead of searching in the US or another continent."
"The initial setup and pricing could be improved."
"CockroachDB needs to improve store processes."
"The closer they can make CockroachDB to being completely compatible with Postgres, the better. It's almost compatible, but not completely. If it was, it would be nice to just be able to use Postgres libraries without any fiddling."
"Cockroach does not support all types of protocols. I need to improve it myself to support a CouchDB on my network."
"We are looking for more features to support distributed high availability and geo-partitioning."
"I would like CockroachDB to have more compatibility with PostgreSQL, especially with the connection string and technical integrations."
"The product must improve its disaster recovery features."
"MySQL could be improved by adding more automation."
"The solution could be more secure."
"When working with a cluster wide, I have to use the MySQL cluster version."
"In terms of what I'd like to see in the next release, one thing that's always missing is dash boarding. There's no real BI tool for MySQL, like there is in Yellowfin and all the different tools that you get. They all have MySQL connectors, but there's no specific BI tool for MySQL. These open source projects have sprung up, but they're more general purpose."
"As an open-source product, there isn't really any technical support available if you get into trouble or have issues."
"Clusters are hard to perform so we use no SQL alternates like MongoDB."
"The analytics features are in need of improvement."
"I would like to have the ability to cancel a query in SQL Developer."
 

Pricing and Cost Advice

"The pricing is good but can be made cheaper. I would rate the pricing a five out of ten."
"I've used CockroachDB at a small scale on the free accounts because we are only testing."
"The platform is affordable even for the enterprise version. It provides value for investment in terms of performance."
"The solution's pricing is not cheap. However, the good thing is that customers are willing to pay for it if they want it."
"The product's price depends on the user's company and the contract model they enter into with CockroachDB. Depending on the contract model one enters into with CockroachDB, the product may or may not be expensive."
"We are using the free community edition of MySQL."
"The tool is open source."
"There is a license for this solution. A lot of the time the solution gets bundled with other hardware or software purchases."
"MySQL is free."
"It has a community version."
"I would rate the solution’s pricing a six out of ten. The solution is not cheap but it’s a fair value. The pricing depends on the use cases of our customers. Some of our customers use the community edition which is license free and a good fit for their use cases. However, we encourage our bigger customers to sign up because of the scalability issues. The paid versions get direct technical support from Oracle."
"I use a free version at present."
"My company uses MySQL's corporate licenses."
report
Use our free recommendation engine to learn which Relational Databases Tools solutions are best for your needs.
824,053 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
40%
Computer Software Company
14%
Retailer
5%
Manufacturing Company
4%
Computer Software Company
16%
Financial Services Firm
11%
Manufacturing Company
7%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about CockroachDB?
The subset of SQL that my client is using is completely supported.
What needs improvement with CockroachDB?
I would like CockroachDB to have more compatibility with PostgreSQL, especially with the connection string and technical integrations.
What is your primary use case for CockroachDB?
I am studying how to deploy CockroachDB and YugaByteDB, and learning some basic information about them. I am testing these databases as part of my school application to find a suitable database for...
Why are MySQL connections encrypted and what is the biggest benefit of this?
MySQL encrypts connections to protect your data and the biggest benefit from this is that nobody can corrupt it. If you move information over a network without encryption, you are endangering it, m...
Considering that there is a free version of MySQL, would you invest in one of the paid editions?
I may be considered a MySQL veteran since I have been using it since before Oracle bought it and created paid versions. So back in my day, it was all free, it was open-source and the best among sim...
What is one thing you would improve with MySQL?
One thing I would improve related to MySQL is not within the product itself, but with the guides to it. Before, when it was free, everyone was on their own, seeking tutorials and how-to videos onli...
 

Comparisons

 

Learn More

 

Overview

 

Sample Customers

Baidu, Kindred, Tierion, Heroic Labs, Gorgias
Facebook, Tumblr, Scholastic, MTV Networks, Wikipedia, Verizon Wireless, Sage Group, Glassfish Open Message Queue, and RightNow Technologies.
Find out what your peers are saying about CockroachDB vs. MySQL and other solutions. Updated: December 2024.
824,053 professionals have used our research since 2012.