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

MySQL vs SingleStore comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

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

Customer Service

Sentiment score
6.3
Customers appreciate MySQL's extensive online resources and community engagement, often resolving issues quickly without needing expensive technical support.
No sentiment score available
 

Room For Improvement

Sentiment score
5.3
The system needs improvements in setup, security, scalability, usability, documentation, support, performance, integration, automation, and cost-effective licensing.
No sentiment score available
 

Scalability Issues

Sentiment score
8.3
MySQL is cost-effective, flexible, scales well for small to medium applications, and integrates with various tools and languages.
No sentiment score available
 

Setup Cost

Sentiment score
8.9
Enterprise users favor MySQL's Community Edition for its cost-effectiveness, while its Enterprise version is competitively priced and budget-friendly.
No sentiment score available
 

Stability Issues

Sentiment score
7.9
MySQL is highly stable, reliable under heavy load, with fast recovery and strong security, praised for its long-standing reputation.
No sentiment score available
 

Valuable Features

Sentiment score
8.3
MySQL is a cost-effective, open-source database offering stability, scalability, security, and broad compatibility, ideal for varied applications.
No sentiment score available
 

Categories and Ranking

MySQL
Average Rating
8.2
Reviews Sentiment
7.5
Number of Reviews
147
Ranking in other categories
Open Source Databases (1st), Relational Databases Tools (4th)
SingleStore
Average Rating
8.8
Reviews Sentiment
7.1
Number of Reviews
7
Ranking in other categories
Database as a Service (DBaaS) (7th), Vector Databases (12th)
 

Mindshare comparison

While both are Databases solutions, they serve different purposes. MySQL is designed for Open Source Databases and holds a mindshare of 19.6%, down 20.7% compared to last year.
SingleStore, on the other hand, focuses on Database as a Service (DBaaS), holds 1.2% mindshare, up 0.8% since last year.
Open Source Databases
Database as a Service (DBaaS)
 

Featured Reviews

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.
Hitesh Kunchakuri - PeerSpot reviewer
A reasonably priced product that offers good speed and seamless support
Currently, I can't think of any areas that require improvement because SingleStore was recently launched in the market. The product can be developed further to provide more appropriate output to users as it is one of the areas where there are shortcomings. The current SingleStore model provides output based on the RANK function. If a user searches for a liquor bottle, then with all the data the product has, it will search for the liquor bottle in the data, and based on a match, the product has an algorithm to rank the product because of which the paragraph that has the best match will be ranked as a 100, the next one as 99, following which the next product will be ranked as 98 and so on. The output from the solution will fetch you all the 100 products that are available in a store, but sometimes a user might require a product with a 97 or 98 percent match from the DB, meaning the product doesn't always work to provide a 100 percent match, an area I feel that can be optimized in the product. Currently, SingleStore's features are excellent as it can read documents, images, and everything. The product works seamlessly for me.
report
Use our free recommendation engine to learn which Open Source Databases solutions are best for your needs.
816,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
16%
Financial Services Firm
11%
Manufacturing Company
7%
Government
7%
Financial Services Firm
30%
Computer Software Company
14%
Manufacturing Company
6%
Healthcare Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

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...
What do you like most about SingleStore DB?
The paramount advantage is the exceptional speed.
What is your experience regarding pricing and costs for SingleStore DB?
Using it for analytical purposes can be cost-effective in the long run, especially in terms of infrastructure. While building an on-premise cluster incurs an initial cost for servers with ample RAM...
What needs improvement with SingleStore DB?
There's a noteworthy consideration when it comes to collecting massive amounts of data. It is not the optimal choice for direct data collection through queries, and it's more suited for aggregation...
 

Comparisons

 

Learn More

Video not available
 

Overview

 

Sample Customers

Facebook, Tumblr, Scholastic, MTV Networks, Wikipedia, Verizon Wireless, Sage Group, Glassfish Open Message Queue, and RightNow Technologies.
6Sense, ADNOC, Adobe, Akamai, CARFAX, Cigna, Cisco, Comcast, DBS Bank, Dell, Dentsu, EY, FirstEnergy, GE, Goldman Sachs, Heap, Hulu, IMAX, Kakao, Kroger, LG, LiveRamp, Lumana, NBC, OpenDialog, Outreach, Palo Alto Networks, PicPay, RBC, Samsung, Siemens, SiriusXM, SK Telecom, SKAI, Sony, State Street Financial, STC, SunRun, TATA, Thorn, and ZoomInfo.
Find out what your peers are saying about Oracle, PostgreSQL, Firebird and others in Open Source Databases. Updated: October 2024.
816,406 professionals have used our research since 2012.