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

Infobright DB vs MySQL 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:
 

ROI

No sentiment score available
Sentiment score
5.5
Many users find MySQL cost-effective and beneficial, appreciating its open-source nature, no licensing fees, and effective resource utilization.
 

Customer Service

Sentiment score
6.8
Infobright DB's customer service is praised but support experiences vary, with challenges accessing developer-level assistance noted.
Sentiment score
6.3
Customers appreciate MySQL's extensive online resources and community engagement, often resolving issues quickly without needing expensive technical support.
 

Scalability Issues

Sentiment score
6.5
Infobright DB's scalability varies, with some users facing limitations and others finding it effective for single-server deployment.
Sentiment score
8.3
MySQL is cost-effective, flexible, scales well for small to medium applications, and integrates with various tools and languages.
 

Stability Issues

Sentiment score
6.9
User experiences with Infobright DB's stability vary, highlighting issues like system hangs and shutdowns, with others reporting stability.
Sentiment score
7.9
MySQL is highly stable, reliable under heavy load, with fast recovery and strong security, praised for its long-standing reputation.
 

Room For Improvement

Infobright DB needs improvements in scalability, performance, integration, and replication to better handle big data and complex queries.
The system needs improvements in setup, security, scalability, usability, documentation, support, performance, integration, automation, and cost-effective licensing.
 

Setup Cost

Infobright DB pricing is seen as expensive, notably for enterprises, with costs varying by server; Community Edition suits non-production.
Enterprise users favor MySQL's Community Edition for its cost-effectiveness, while its Enterprise version is competitively priced and budget-friendly.
 

Valuable Features

Infobright DB offers high compression, fast analytics, and SQL compatibility, excelling in big data handling and scalable deployment.
MySQL is a cost-effective, open-source database offering stability, scalability, security, and broad compatibility, ideal for varied applications.
 

Categories and Ranking

Infobright DB
Ranking in Relational Databases Tools
33rd
Average Rating
7.6
Reviews Sentiment
6.4
Number of Reviews
10
Ranking in other categories
Data Warehouse (26th)
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 Infobright DB is 0.2%, up from 0.2% 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

SD
If you need a real big data solution, look for a distributed solution that actually has a proven track record.
This version of Infobright has zero support for distributed scalability. The internal smart grid employed for each table has a major flaw in that the data size cannot be expunged until 2GB of data is reached at the column-level. This is a major flaw, making usage in a big-data scenario impossible. This means that you can delete as many records from a database table as you want. However, unless the 2GB aggregate size threshold was reached for some of the columns in the table, no reduction in disk space usage will occur. Only the data from the columns that reached 2GB will actually decrease. Other columns below 2GB in size do not leave the disk. I spent countless hours trying to find some workaround for this. I have nightmares of my e-mail inbox full of unsolvable questions about data size reduction from our field engineers.
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.
report
Use our free recommendation engine to learn which Relational Databases Tools solutions are best for your needs.
824,067 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
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

Ask a question
Earn 20 points
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

No data available
 

Also Known As

Infobright
No data available
 

Overview

 

Sample Customers

REZ-1, SonicWALL, IntegriChain, Fuseforward International Inc., Polystar, Live Rail, Mavenir Systems, JDSU Partners, Bango
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 Infobright DB vs. MySQL and other solutions. Updated: December 2024.
824,067 professionals have used our research since 2012.