MySQL Reviews

I use MySQL as middleware to get the extracted data from the database. I work with MySQL as an administrator to set up the whole platform. And I document the recipe for setting up the MySQL database.

We are working with the latest version.

SQL is just a relational database. It is open source. It's pretty good. I have been using it for a long time.

Because I am the middleware guy I'm not the SQL database administrator. If I have any issue with it, I'm going to contact the right person. Sometimes, not because the version is not the latest version, there are some issues with it. Sometimes there's an issue with the server which creates issues with it. Then, when the administrator checks the status and makes notes, it works normally and the problem is fixed. With a big company you are not going to work directly with the MySQL database. We are the end user and not the administrator of the SQL database.

For MySQL, in terms of the usage or as the end user, I don't have much to recommend, as long as the query latency meets your requirements, it will be great. Otherwise, it's the horizontal scalability and you get more parallel in the implementation in terms of the SQL database regardless of the usage. This is probably much better than the vertical in terms of scalability.

I have been using MySQL this year.

If you are working in the cloud platform then you do have scalability because the cloud platform is usually AWS or GCP, and they provide this kind of scalability. If you get some issues with the query and latency or something like this, that is an issue of scalability and you can just adjust the horizontal or vertical scalability to meet your requirements.

But the company I was working with was a very big company. It's more than several thousand people and they usually have a lot of data that they are going to store in the MySQL database. They gather the data from the SQL database and then transfer it like ETL and you get data from all the different distributed systems and then put them into the centralized MySQL database. After that you're going to visualize this kind of data so that you can use the Power BI or that kind of tool to generate reports or to create a dashboard for the system. This company had its platform on-premises, but right now they are moving these technologies to cloud. That's why I'm talking about the scalability in two different ways cloud and on-prem.

For technical support, I'm the end user so I extract data or visualize the data from the SQL database. I didn't get too into the daily maintenance of the database.

The initial setup for the SQL database is not complex and it even integrates into the platform. You set up the recipe and then just follow the build book. Then it works as long as you follow the procedures.

Regarding the price, because it's the open source they have different licenses. Even for open source there's a license for the enterprise. I don't think it is expensive. Also for the scalability in the cloud, the price is based on the usage, such as, how much data you transfer.

For the best usage right now, the trend is to move the platform from on-premise to cloud. Then, you you really have the best flexibility to scale down or scale up based on your usage. You can make full use of the resources and then pay for whatever you use. Because if you have it on-premise you always pay the same price no matter how much usage you have. So one of my suggestions is if you plan to set up the platform for MySQL, it would be best to go directly to the cloud solution.

On a scale of one to ten, in terms of the usage for the middleware team and the end user of the SQL database, I would say it's around an eight at least. I cannot say from a  database administration perspective.

To determine what would allow me to give it a 10, I would first have to get more experience using it on the cloud version.

We are doing POCs for our clients in our testing lab, and if a POC is working fine, then we give it for the production release. 

It has a lot of features. The RDBMS, consistency, and multi-user features are valuable.

We want high availability and replication features, which are currently missing in this solution. It would be great if they can provide an in-built replication feature, similar to Oracle RAC, in MySQL.

I have been using this solution for the last two years.

It is a stable RDBMS. There is no doubt about that.

We have been using it for POCs. It has been consistent for a hundred users. Currently, we have three groups that use this, and each group has 20 users.

I have not contacted their technical support.

It is open source. We prefer it for POCs because it saves the license cost.

I would rate MySQL an eight out of ten.

We are an asset management product company. Our product is deployed on the cloud and the backend database for it is MySQL.

The technical support should be more knowledgeable and available worldwide.

We have been using MySQL for the past five to six years.

So far, it has been pretty stable and I haven't had any problems. We plan to continue using it in the future.

MySQL is very scalable, so I don't expect any challenges.

We have a contract with a third-party for support. So far, it has been working fine for us and I don't see any challenges. That said, having worldwide support is something that would be an improvement.

Prior to MySQL, we did not use another database for this purpose. We built our core product directly on top of MySQL.

The initial setup seemed pretty decent, so I don't see any challenge in that regard.

Our in-house DBA team installed it. We have one DBA and one junior.

This is a good product and I recommend it to others.

We use it as a data store and from that perspective, we get everything we need. We don't have any complaints about features such as analytics, reports, or dashboards.

I would rate this solution a six out of ten.

The main reason that customers pick MySQL is that it's cost-efficient.

Apart from the features that are in the enterprise part, we find the database to be
valuable. The connectors and the backup features are valuable as well. We use the
basic database. We don't really use the extra features. Our clients like the security
features in the database.

We would like to see more security.

I have been using MySQL for three years. 

My customers haven't mentioned having any problems with stability. 

Scalability is good enough.

I haven't contacted Oracle in regards to MySQL but I have contacted Oracle support for other things. They're okay but from my end, the problem is that they're not proactive. From one to five, I would rate them a four. 

There's a lot of documentation on the Oracle support portal even though you must be contracted customer. There is also a lot of support information on the community portals and google search in general. This is the reason we picked MySQL from the rest.

The initial setup isn't so complex. You have to get a lot of support from the
community. From my end, it's not so complex. You should consult with the
community.

My experience has been open-source. Oracle should start putting in some of the enterprise features in the standard version. There are some key features that should be part of the standard. Things like replication should be part of the standard version as opposed to it being in the enterprise version.

ACID attributes are the most valuable feature, as data reliability is a top concern.

The backend of the production traffic happens at this level.

The dynamic scalability, clustering, dynamic replicas safeguard against failures, ease of setup and use all need to be improved.

• MySQL was originally meant for a single server; now with the 5.7 version, they have introduced the multi-master model but it is on the user to ensure that there is no conflict of data. Also, to add/remove a server from the cluster requires downtime and MySQL won't scale load on its own as it has scaled up/down (the load distribution has to be done on a separate layer).
• MySQL does not understand the clustered model, it is not aware of others in the cluster and won't act as a player in the cluster.
• Data corruption or two different updates to the same record are not sorted in the replicas and needs manual intervention.
• The cluster setup is complex and so is its maintenance.
• It is not equipped to take advantage of the Cloud (AWS, Azure etc) and their pricing models (go as you use).

I have used this solution for two years.

We have seen the corruption of data in replication when used with filters and also, with the growing data response time dwindles.

A lot of manual effort is needed to scale the solution; a lot of room for improvement is there.

The setup was of mid-level complexity.

It is a GPL license, only the support is priced but as there is a good community so buying support is optional.

I wasn't involved as this predates me at the organization, but today if this re-happens MySQL won't be the best choice.

Do your research and make sure for your use case that MySQL is the best choice, before making any commitments.

With most open source products we were building, even the language was open source, such as that which employs PHP. This is where the MySQL free version was being primarily used by many of the clients in the storing of their data. 

There have been some great shoppers which we built with the solution. We use the solution to store the transactional data that we receive from various sites or have the data stored in MySQL. 

The solution is easy to use. As the query patterns are very similar to SQL, this simplifies the use and understanding of the solution. 

Integration is a key feature in need of improvement, as we have spent hours building this just to ensure that a set of data is exposed to a different client, a different world in need of that data. Since we are dealing with open source, which we are now employing in memory databases as well, it would be nice if they were to start thinking along those lines. 

I have been dealing with MySQL for around a decade. 

I have found the free version to be stable. 

I have not made use of technical support. 

I was not involved in either the installation or deployment strategy. 

While I was not involved in those projects over the past year, we do have a couple of clients who choose to use the paid, enterprise version of the solution and who take full advantage of it.

While the solution has, nowadays, moved to the cloud, the one I have been dealing with is on-premises.

Even though the solution has not been off the market, I do not possess the exact figures of those making use of it. It is still being used by a couple of our clients. 

I would recommend the solution to those interested in using the free, stable version of the solution which incurs no licensing costs. 

I rate MySQL as a seven out of ten. 

We use MySQL for internet applications. 

MySQL is easy to integrate. It works with just about every language. 

Security is a concern. MySQL could have better security features. 

I've been using MySQL for several years. 

I've never contacted technical support. It is done on the internet. You have all the support there.

Setting up MySQL is no problem at all. I can do it by myself, and it's deployed almost instantly.

I would rate MySQL nine out of 10. 

I use MySQL to teach students about databases. They implement projects using this product.

MySQL is lacking some of the features that you find in a commercial product, but it is sufficient for basic functions.

This product is a good teaching tool for students who want to learn about networked databases.

The documentation is pretty weak and should be improved.

The GUI for PHP MySQL Admin can be improved because it is not very flexible and sometimes difficult to use.

I have been using MySQL for more than five years.

I have experience with other full-scale databases, such as PostgreSQL. For use cases where I need full functionality, I would use another product.

I am using the Community Edition, which is available free of charge.

I would rate this solution an eight out of ten.