MySQL was open-source at the beginning until Oracle acquired it in 2010. I started working with MySQL because I was an Oracle expert, having worked for Oracle for eight years. That's why I added MySQL to my skills as an administrator. MySQL is a powerful database engine that is easy to install, manage, and work with. It's ideal for fast application deployment and is cost-effective as well.

MySQL
JetwareExternal reviews
External reviews are not included in the AWS star rating for the product.
Open-source solution to store data of hardware servers and their configurations
What is our primary use case?
How has it helped my organization?
MySQL is for metadata and data. My organization has used it to store data about hardware servers and their configurations, including network and storage configurations. MySQL is an RDBMS engine, so it can be used for any business application.
What is most valuable?
MySQL has a straightforward installation process, is lightweight, and easy to manage. Compared to its competitors, it is more accessible and user-friendly. While competitors like Oracle are known for their extensive features, they are often more complex to install, configure, and maintain, requiring experts to manage them, which can be costly. MySQL, now owned by Oracle, may not have the same feature set as Oracle's flagship database, but it is simple to install, manage, and cost-effective. MySQL is a viable option that can be enhanced with additional features, making it reliable for small to medium-scale applications and capable of effectively handling substantial amounts of data.
What needs improvement?
MySQL is now in a real application cluster. In terms of high availability, MySQL can be configured for active-active or as a real application cluster.
For how long have I used the solution?
I have been using MySQL for ten years.
What do I think about the stability of the solution?
When MySQL is involved in the metadata, it never gets down. It's very stable.
What do I think about the scalability of the solution?
It's secure. MySQL supports large databases that can contain nearly fifty million records. It also supports up to sixty-four indexes per table.
How are customer service and support?
They provide 24/7 support. It provides faster resolution and identification.
How would you rate customer service and support?
Positive
How was the initial setup?
It is very easy to install and takes an hour to complete.
I rate the initial setup a ten out of ten, where one is difficult and ten is easy.
What's my experience with pricing, setup cost, and licensing?
It is open-source and supported by Oracle.
What other advice do I have?
Oracle occupies it, so Oracle added more security features, such as password system improvements, host-based verification, and encryption, to the MySQL engine. It's developed and managed by a big company, and they keep adding new features.
I recommend another solution for large data, like billions of records. However, MySQL is a good option for data up to about fifty million records.
Overall, I rate the solution an eight out of ten.
Lightweight and is available at a friendly price
What is our primary use case?
Right now, I don't work very effectively with the tool. I am more like an architect currently, so I don't have to go deep into MySQL. In my company, we don't use Azure yet. Teamcenter PLM software is set up using Oracle or MySQL. We need to install Oracle or MySQL.
I used the tool for technical things for ten to twelve years. Right now, I have lost touch with how to use it.
What is most valuable?
The product is cost-effective, less expensive, and much faster, considering the way my company structures the data and the solution handled. The only thing is that if there are 10,000,000 or 20,000,000 records, it will slow down a bit. If the data is less, the performance is good. Once the data keeps on increasing, such as if we work with five terabytes of data and go up to nine terabytes of data, MySQL finds it difficult to handle the data. Huge amounts of data can only be managed by Oracle.
What needs improvement?
The performance issues in the product can be considered as an area where improvements are required.
For how long have I used the solution?
I have experience with MySQL.
What do I think about the stability of the solution?
It is a stable solution. Stability-wise, I rate the solution a nine out of ten. Once the data increases, the tool will face some issues.
What do I think about the scalability of the solution?
Scalability-wise, the product works very well. I rate the solution's scalability an eight out of ten.
My company usually deals with big companies having a minimum of around 2,000 people.
How are customer service and support?
I have not contacted the product's support team since everything is available on the internet.
Which solution did I use previously and why did I switch?
I used Dropbox when it was initially introduced. I had put so many documents into Dropbox, but I stopped using it. It has been a long time since I have used the product. I had used the product when it was launched, and the tool was giving two GB or three GB for free.
How was the initial setup?
The product's initial setup phase is very easy. I rate the initial setup phase a nine to ten out of ten.
What's my experience with pricing, setup cost, and licensing?
My company uses MySQL's corporate licenses.
What other advice do I have?
In terms of our organization's data management strategy, especially if I talk about PLM software, which is about data management and can be regarded as the core data management of the products that we make. When we are designing something, specifically a new product, it is a critical area, especially considering that I am in the energy sector. In the energy sector, when we are building huge turbines and other things, the data might have intellectual property aspects attached to it. Even within the company, one region cannot see other regions to the extent to which the product offers security. In my company, we use PDM and PLM from Teamcenter effectively.
MySQL is not a tool my company uses in production. When we create some small demos, we use MySQL. For production, we would use only Oracle because it is the most stable tool in the market.
When we install Teamcenter, we don't need to touch the database. We just need to make some references to figure out this is the database, and it automatically creates everything. The basic thing about PDM and PLM systems is that the user should never touch the database because people may corrupt the data model or do anything that will have a very bad impact on the system. Database modifications only have to be made to the PLM system. We are not supposed to interact with the database directly.
The tool is very lightweight, less expensive, and sometimes it is free. It is a very usable tool that is preferred by a lot of people. Only for production use, I may ask people not to use it.
Integration of MySQL is like how we don't directly integrate PLM with Oracle. We have to use PLM's APIs to talk to the database. As a part of the best practices, we should not directly integrate anything with the PLM database. Feature-wise, the integration capabilities of the product are easy to use. It is like any other tool where if there is a table, there is a property. If you want to map a property using any middleware, then we can easily do that.
I recommend the product to others. For medium-sized companies, MySQL is one of the best solutions. Medium-sized companies can choose not to go for Oracle, which is very expensive.
In terms of the value or benefits derived by our company from the use of the product, I would say that it is not very expensive and provides performance along with scalability. The product can cater to the needs of customers ranging from 2,00,000 to 6,00,000 to 10,00,000 records. Even 20,00,000 records are fine, but after that, users may get into trouble. It is the best tool for mid-sized companies with a reasonable amount of data.
I rate the tool an eight out of ten.
Best DB for storing all kind of data.
MySQL: Easy and Powerful
We can use mysql for small scale projects. I had previously used in many beginner level projects. There are also lot of forums that help to troubleshoot any issues.
Intense but rewarding
Beginners Relational Database
Also daily operation like UPDATE, TRUNCATE, GRANT etc., were done on the work bench itself
Provides powerful data querying.
What is our primary use case?
We are developers working on different types of projects. We use relational databases in some projects and non-relational databases in others. When we use relational databases, we use MySQL. When we use non-relational databases, we use our DynamoDB or MongoDB.
What is most valuable?
- Ease of Use: MySQL is relatively easy to set up, configure, and manage, especially with tools like MySQL Workbench and command-line utilities. Its widespread popularity also means there is ample documentation, tutorials, and community support available for users.
- Open Source and Cost-effective: MySQL is open-source software, which means it is free to use and can be customized according to specific requirements. This makes it a cost-effective choice for startups, small businesses, and projects with budget constraints.
What needs improvement?
Compared to some other database systems, MySQL may have limitations in terms of advanced features and functionalities, especially when it comes to complex data relationships and transactions.
For how long have I used the solution?
I have been using MySQL for two years.
What do I think about the stability of the solution?
In my past two years of MySQL experience, I found no bugs or breakdowns. It works completely fine.
What do I think about the scalability of the solution?
Many cloud providers offers managed mysql service with scalable architecture ,automated backups , monitoring and scaling. Leveraging this can solve the scalability problem.
How was the initial setup?
MySQL is very easy to install and use.
What's my experience with pricing, setup cost, and licensing?
As it is an open source and there is community edition available so if you have small or medium use case it is much cheaper to use.
What other advice do I have?
Below are some thing to consider while working with mysql.
1. Regular maintenance
2. Security consideration
3. Version compatibility
You can try MySQL if you have any use cases of relational databases. It is very easy for somebody to learn to use MySQL for the first time. The solution worked fine for me, with no breakdowns or scalability issues.
Overall, I rate MySQL eight and a half or nine out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Easy to manage, saves time, and provides good documentation
What is our primary use case?
I use the solution for personal use cases like software development, mostly database bug systems.
How has it helped my organization?
I used the tool to build our website. It is used as a database to store information.
What is most valuable?
SKIP LOCKED is a valuable feature. It prevents us from deleting things we put in the database. It's mostly for background jobs in the software development site in MySQL 8. It is a new feature. The solution easily integrates with other tools and systems in our IT environment.
What needs improvement?
The full-text search feature must be improved.
For how long have I used the solution?
I have been using the solution for the past three weeks.
What do I think about the stability of the solution?
I rate the tool’s stability an eight out of ten. We can create a database user schema. It's quite easy to update and remove in case anything happens. Backing up is quite easy. We have security features for the backup.
What do I think about the scalability of the solution?
I’m the only user in my organization.
How are customer service and support?
The product provides good documentation online.
How was the initial setup?
It is easy to deploy the product. I deployed it on my own. The deployment took an hour. We deploy the product using Kamal. It uses Docker. The tool is deployed on the cloud. To deploy the solution, we just have to enter the password in the server and deploy it. It wasn't much of a hassle.
What was our ROI?
The tool is easy to manage and saves us time. It has much less complications.
What's my experience with pricing, setup cost, and licensing?
We're using the community version. The tool is open source.
Which other solutions did I evaluate?
I also use PostgreSQL.
What other advice do I have?
The tool helps us get the job done. It is not very complex. Overall, I rate the product a nine out of ten.
Easy to use, code is easy to write and understand
What is our primary use case?
I don't use MySQL extensively, but I use the code within MySQL for preparing some reports and all that.
What is most valuable?
Code is easy to write and code, it's easy to understand. That's why it's widely used. The queries are very easy to understand and [write the] code. For coding, it's very easy.
What needs improvement?
The user interface could be more user friendly. Mainly because most of the times we see black and white digital lines. Something like Python.
For how long have I used the solution?
I have been using it for three years. I have been using it since 2021.
What do I think about the stability of the solution?
I haven't experienced any bad things.
What do I think about the scalability of the solution?
It is widely adopted in our company. We have around 60% of our total employees using it.
How are customer service and support?
We have an internal support team. We usually connect to them, and they will resolve the issue. We don't need to connect to the MySQL team directly.
How was the initial setup?
The initial setup is not very difficult. It's easy only.
What's my experience with pricing, setup cost, and licensing?
The pricing is not much expensive, it's cheap only.
What other advice do I have?
I would recommend it. For beginners, it is pretty much easier compared to other tools. The queries are very similar and easy to learn in a short span of time.
For beginners, it is very easy to use. It would be something easy to learn. It is a perfect tool for beginners.
Overall, I would rate the solution a seven out of ten.
Easy to use and can be used to store data
What is our primary use case?
MySQL is an open-source relational database management system used to store data.
What is most valuable?
MySQL is an easy-to-use solution that provides stability, reliability, flexibility, performance, security, and high availability.
What needs improvement?
MySQL could introduce more indexing strategies. There are a couple of strategies where you can index things to be more searchable and visible. We lack that kind of functionality. For example, if your name is indexed correctly with a certain strategy, it can improve the search results faster. The solution’s interface could be improved.
For how long have I used the solution?
I have been using MySQL for my entire career.
What do I think about the stability of the solution?
MySQL is a stable solution.
What do I think about the scalability of the solution?
MySQL is a scalable solution.
How was the initial setup?
The solution’s initial setup is easy.
What's my experience with pricing, setup cost, and licensing?
MySQL is a free and open-source solution.
What other advice do I have?
MySQL is deployed on the cloud in our organization. Big companies like Netflix, Uber, and Facebook use the solution. Since MySQL is an old product, many people might have faced similar issues, posted them online, and got a resolution. MySQL's performance and scalability features have supported our database growth.
New users can follow the documentation to use the solution, as it is straightforward. You need to be very clear about why you want to use the solution. MySQL is a relational database management system that cannot be used as a dynamic database management system.
MySQL is generally faster and more efficient than other relational database management systems. Hence, it is our preferred choice for applications that require high performance.
Overall, I rate the solution a nine out of ten.