MySQL Reviews

We primarily use the solution for the many small applications we use. However, we do not use it with our enterprise-level applications.

The solution is very simple. It's easy to use. That's the most important feature. 

We do have it supported by various programs we run with it.

The replication needs improvement. It's becoming a native cloud product like Oracle DB or Cockroach DB.

We started using MySQL in various products about 10 years ago when it was still an independent community product.

The solution has proven to be quite stable. We haven't experienced any bugs or glitches.

According to our experience, it's not really an enterprise tool that you can easily expand and scale the way you can with, for example, Oracle. It's good for small to medium-sized applications. It is not ideal for very big applications.

We have a data center that uses the application and it isn't very heavy on traffic. It basically runs on its own. We only use it occasionally. It's like a co-operation management system.

We do plan to increase usage, but we plan on looking at different databases. We're in the process of researching how scaling up would work. Chances are, we'll need to move to a different platform.

We've never been in touch with technical support. For us, so far, things have been working perfectly so there hasn't been a need to.

This is the first solution we've used. We don't use any other product. It's very popular with the in-house program, as we advised them to stick with this application.

We've used the solution for ten years and the setup hasn't changed much over time. It is, more or less, simple when you compare it to other databases. 

Deployment takes less than an hour.

It only takes one person to maintain the solution. The individual doesn't have to be an engineer. They just need to be a support person.

We don't need a consultant for the implementation. This is used by someone in our company that uses databases and has an average knowledge of the product. We don't even need a vendor. We can handle setup ourselves at this point. It's not like Oracle or other products that can be quite complicated.

We use the community edition of the solution.

We didn't evaluate anything before choosing this solution. However, there are a few new products coming up that are growing in popularity and we will need to research them. Products like the Cockroach DB, Nuo DB, etc. are on our radar to be evaluated in the future.

The most important thing other potential users need to do is to look at the use cases for this application and to evaluate how it's able to handle heavy loads, etc. Users should evaluate how it handles high-traffic. They'll need to ask themselves: is the solution usable for my applications? 

I'd rate the solution seven out of ten.

We utilize the DB as a data-repository solution for our front-end applications. The solution gives us the ability to run numerous instances on various geographical cloud servers.

Yes, MySQL has improved numerous processes; it has given us the ability to create applications without absorbing major costs.

• Its ease of use
• It's secure.
• It's fast.
• It has high-end processing.
• It can distribute across clouds.
• It has the ability to run on any operating system.

• I think a better front end would be a better solution (web application front end, similar to what Red Hat is doing to Fedora). 
• Another nice solution for MySQL clustering would be the use of Webmin. 
• Also, security measures could always be improved, and the clustering process could be enhanced as well. I recommend using UFW, iptables, and firewalld.

The solution works extremely well. It is easy to install and works on any platform. The price is good because we utilize various versions of the software/DB.

If the user sets up DB up using MySQL Cluster (creates a grid type of design), then we find the solution from a hardware perspective using NVMe, NVMe-oF, 10GE network connections, and 32-100GB of DDR4 memory (dependent upon customer requirements). 

Scalability can be initiated using high-speed connections across IPv6 connections (IPSec AES-256 ESP/AH VPN connections without purchasing VPN concentrators — this can be done at the network layer).

We use various versions, but most of the time this is based on the client's requirements.

After the initial training, the installation worked pretty well. I would suggest setting it up in a lab. This gives the user room to test the installation and configuration process. It is recommended to use PhpMySQLadmin — (https://www.phpmyadmin.net) — after the installation process is completed.

It was implemented in-house. Most of the applications are tested in our cloud and on-premise servers.

60% ROI (There are DLs — direct labor costs and overhead costs, but once it is set up, we image the configuration and deploy our designs in docker).

I would suggest testing MariaDB before jumping in. This will give the user the ability to test the DB before using it. It is very easy to set up. MariaDB is free, and licensing is based on GNU.

N/A.

I would suggest running tests against MySQL, MariaDB, Oracle, PostgreSQL, and MS SQL to determine which one best suits your needs (cost, development, and integration should all play in your decision-making process).

I used it to obtain insight into the entire network and the resources being utilized. The current GUI lets us see the traffic happening east to west and the total bandwidth consumed by it.

• It provides visibility, where something was either broken or in pieces only.
• It creates a unified view of the entire architecture and performance factor, helping to manage the network more easily.
• It has a remote access feature to manage the database from a remote location. This enables in-work collaboration.

I have found the following features valuable:

• NetFlow of the whole system
• Information flow and scaling
• Communication between multiple collaborators and stakeholders
• Its user-friendly features.

The only service which could be improved is its usability. The entire user experience needs to be revamped to meet the 2018 design standards.

The overall service is great. 

I use MySQL for employee service in an OLTP database.

I use MySQL for various purposes. Sometimes I have used MyISAM as a storage engine rather than InnoDB.

When working with a cluster wide, I have to use the MySQL cluster version.

The 5.7 version has very better performance improvement over the previous version.

I'm a tester, an optimization tester. It's basically when the developers have the back-end in SQL. We go and test it out for them and check that the table updated correctly, and we do something on the front-end.

To give you an example, initially we didn't have a database server as such, and we had to make use of some database. Now we use something where we can share the instances of the database which were created virtually, which is a very good feature, which I felt has improved our organization.

The most important features would be querying, the query language where you have the data definition or data modification language, as well. In some cases, we have to create our own tables for testing purposes. In that case, having SQL Server is much easier compared to what's available.

I feel that some tools which make it easier to create queries or make it easier for other functions would be really interesting to see.

Pretty much since we have our own in-house SQL branch, the administrators are there, so they take care of the stability with the product. As far as I've seen, there really hasn't been much of an issue with stability.

 It's pretty scalable.

I haven't contacted them, so I have no experience with them. We generally have an internal team which would work on it. So our point of contact is an internal team, rather than going to MySQL.

I've used a lot of different solutions. MySQL is one of the top among them. Usability and scalability are some of the reasons we went with MySQL.

It was pretty straightforward. No hassles with the setup. 

Usually the setup is done by the IT admin guys, but it was pretty straightforward. The IT admin guys had to come in and give us the rights to install it.

I'm not sure about pricing, I don't deal with the pricing. It's an organization decision.

There were many options.

No one tool fits the bill for every company. Do a feasibility study, and get to know what is can do before going in and developing.

Web portal database.

• Free usage
• Performance
• Community

Scaling.

There have been some problems with big table operations.

Some problems with big table operations, and a struggle to keep the servers responding in peak situations.

I don't have enough information about it, as I normally look for community support.

Straightforward, and and easy to run.

Can range from free to quite expensive, depending on the environments and requirements, so better to really set goals ahead of setting it up.

SQL Server, Oracle XE, MariaDB.

It is a stable, reliable, and powerful solution that is quite suited for small to medium organizations and/or projects.

We use MySQL and MariaDB for most part of our mission critical applications

This as it is so simple to integrate with web applications, and other well known applications.

Since it has many integrations to web applications, it is very easy to install and deploy open source web applications.

How it uses clustering.

The API's to PHP, ruby, perl, java, python, and many more high level programming languages makes it easy for us to deploy new features fast.

How to scale out with shard clusters.

The way how to handle replications needs to be improved, as we noticed that there are some performance drop of (using only one core for example)

No issues.

Yes, the binary log replication process in a cluster environment has issues processing data as fast as it arrives.

Customer Service:

A 10 out of 10.

Technical Support:

A 10 out of 10.

We have been using many different types of databases, and will most likely use this one for part of our systems, as it is has so much integration.

The initial setup was easy.

We implemented it in-house.

Free.

Be sure to take backups of the solution, as this will check that the blocks are okay.

We decided to use "DB Protection for MySQL" as it has options to perform block level incremental forever, and integrates well with Spectrum Protect.

Yes, we checked MongoDB, PostgreSQL and MariaDB.

It dramatically improved use for several of my customers.

This depends on my customers' use.

SQL and NoSQL use.

When configured correctly, no stability issues.

When configured correctly, no scalability issues.

Very good.

MySQL Support Services by Percona. I switched to Oracle MySQL services because of a better ROI.

There is no obvious answer. It depends.

Depends on the customer's needs. 

MariaDB, MySQL Support Services by Percona.

Stick with the source, stick with Oracle MySQL as the leading vendor for MySQL technology.