The Industry Standard for Simple Databases
What do you like best about the product?
It is the industry standard for simple databases
What do you dislike about the product?
Scalability and advanced features are better found in other products
What problems is the product solving and how is that benefiting you?
Hosting simple/small databases for applications
Don't overthink it: the answer is probably MySQL
What do you like best about the product?
You can't talk about RDBMS without mentioning MySQL, there are alternatives you could choose to cater to your more specific needs, but for general-purpose managing of relational data, there's a reason MySQL has been the king for over 20 years. It's easy to set up and easy to use.
What do you dislike about the product?
Alternative technologies like Postgres have begun supporting new needs, like sophisticated JSON data support and querying, and more powerful SQL syntax.
What problems is the product solving and how is that benefiting you?
MySQL solves the obvious problem of storing relational data, but does it with speed, operational simplicity, predictability, and affordability, on a tried-and-true, mature platform. Sure there are other DB techs suitable for very specific needs, but for 95% of projects MySQL is all you need.
Reliable, Fast, and Beginner-Friendly Database Solution
What do you like best about the product?
MySQL is reliable and very fast; this ensures DB management is not a challenge. MySQL supports complex queries. Moreover, it is easy to use even for beginners. Its integration with various coding languages and tools is very easy. It is open-source. All in all, it is reliable regardless of whether it is used for small or large applications.
What do you dislike about the product?
Certain complex features require additional setup or software. Handling large databases to scale can be a bit intricate. Backup and recovery operations might require strategic planning. The default storage engines may not always be optimal. Nevertheless, it functions quite well, although sometimes these small issues crop up.
What problems is the product solving and how is that benefiting you?
MySQL addresses the challenge of how to store and retrieve structured data by offering an uncomplicated but reliable relational database system. It enables effective querying, reporting, and integration with applications, including stringent data consistency and security features to protect key information. On the whole, it saves time, improves data management, and supports scalable application development.
Beginner-Friendly, Efficient, and Free—Perfect for Large Datasets
What do you like best about the product?
It's beginner friendly and easy to use. It's free to use under GPL license, cross platform and handles large datasets efficiently.
What do you dislike about the product?
It lacks advanced functionality such as JSON but not as robust as Postgre SQL. Less optimized like RDBMS
What problems is the product solving and how is that benefiting you?
We are using MySql in Salesforce Marketing cloud handling large amount of data and filter out data which is fast and reliance.
The Best Easy-to-Use Relational Database
What do you like best about the product?
Best easy-to-use Relational Database with widely available cloud service providers for Mysql
What do you dislike about the product?
Not as many features reach like PostgreSQL.
What problems is the product solving and how is that benefiting you?
Relational Database needed first ting come in mind is MySql
Simple, Reliable, and Fast with Outstanding Community Support
What do you like best about the product?
It’s simple, reliable, and fast to get working. It has a huge ecosystem and community support.
What do you dislike about the product?
Advanced things like sharding or complex analytics can be awkward compared to newer databases
What problems is the product solving and how is that benefiting you?
This tool addresses the challenge of structured data storage by providing strong consistency and predictable behavior. As a result, my daily development, debugging, and operational tasks become much more straightforward and reliable.
Effortless Manual Database Creation Made Simple
What do you like best about the product?
I can create a organised database manual way
What do you dislike about the product?
I think adding AI features to improve user experience
What problems is the product solving and how is that benefiting you?
It’s very useful for those who are into IT field
Great for Learning SQL and Rapid Query Experimentation
What do you like best about the product?
MySQL serves as a good entry point for someone to learn SQL.
I like to quickly experiment with queries - be it joins, creating views, triggers, procedures, etc. which I use later on in creating Semantic Views for other applications.
What do you dislike about the product?
Saving the data usually requires creating proper tables and having prior insight.
Also having maintenance columns is tricky based on datetime and regions.
UI is also a bit dated and I would love to have capability to edit tables directly and have corresponding SQL generated for this change.
What problems is the product solving and how is that benefiting you?
MySQL helps me with prototyping different application databases. I also use it with my Agentic AI Proof of Concept applications.
Energy analytics views have transformed how our team stores and analyzes device data
What is our primary use case?
In my current role as a software developer, we are using MySQL in one of our old projects and in the new project as well, specifically for storing the device data from energy meters that send voltage, current, and other related information.
Basically, in our project, we have some APIs that our device calls. Once the data is received by the API server, we put it in BullMQ, and from BullMQ, we have set up the consumer that consumes the data and puts it in MySQL. Over MySQL, we built a dashboard to show the energy trend, users, and load averages both device-wise and in groups based on averages. We have created an analytics dashboard for the energy meters using MySQL.
In my work, we use materialized views by running a cron job over the server, utilizing it in two ways: one is from the application server that inserts data into another table for analysis, and the second is for making materialized views where we aggregate data such as daily averages for devices and groups of devices. Inside those views, we store group-wise metrics such as average current, average voltage, peak load, and average kilowatt usage per hour. We also present these views on our dashboard, providing users the flexibility to select devices and create views for real-time rendering.
We use Tata Communications as our cloud provider for this hybrid cloud deployment.
We have used MySQL from the start, as we had experience with it, and it is straightforward to set up and easy to manage with fewer people.
What is most valuable?
One of the best features MySQL offers is the materialized view that I use. Additionally, as it acts as a transactional database, its transactional properties are useful, although they are not much of a concern in our use case since we focus on device data.
The main feature we utilize in MySQL is the view, and I can say that it is the most valuable feature for our needs.
My organization has experienced positive impacts from MySQL, as it provides exceptional capabilities.
What needs improvement?
MySQL can be improved. While I do not see any significant improvements needed for MySQL in my use cases, I would consider it if any arise in the future.
For how long have I used the solution?
I have been using MySQL in the industry for two and a half years, and I used it for approximately three years during my college time.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
MySQL's scalability is currently adequate, as we have increased operations from ten thousand to twelve thousand devices, and it is working fine for us, but we will monitor for any future issues.
How are customer service and support?
We have not needed to reach out for MySQL's customer support, as the community provides solutions for any issues we face.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I have evaluated other options such as PostgreSQL, as it is better for analytics queries, but its primary and secondary index concept makes updates slower compared to MySQL, which leads us to use MySQL.
How was the initial setup?
The initial setup for MySQL is straightforward and easy to manage with fewer people.
What was our ROI?
I have seen a return on investment with MySQL, as it allows us to manage with fewer employees, focusing on business logic rather than database management.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for MySQL has been good.
What other advice do I have?
I rate MySQL a nine out of ten. I choose nine out of ten because while there should always be room for improvement, I do not see any necessary adjustments in my use case since it is working fine.
I advise others considering MySQL to start with it if they have small teams and are undecided about which database to use. It is easy to set up and allows you to focus on your business logic initially without going for more complicated databases.
MySQL meets our expectations for our use case so far. We will see what the future holds. My overall rating for MySQL is nine out of ten.
Learning projects have benefited from open source flexibility and strong documentation support
What is our primary use case?
I used MySQL mostly for college projects. I have used Postgres, but for the use case that I utilized it for, I do not think it was interchangeable with MySQL. To be frank, I do not really know the nuances.
What is most valuable?
The best features with MySQL are the fact that it is open source and a relational database. The best part about using MySQL was that it was open source, so it was pretty easy to understand and get materials to learn.
MySQL has good documentation and online support. It is pretty good in terms of integrations, continuous integrations with different tools, and customization options.
What needs improvement?
MySQL was not scaled up, so I did not use the replication capabilities. I do not think MySQL's data security features were at an industrial level for my project, so I did not make use of them. I was mostly using indexes.
I would advise people thinking about using MySQL to look up if the indexing mechanism is useful for their needs and then accordingly select the right database, and also consider if relational databases make sense for their use case. MySQL uses B-trees, so indexing could not be relevant to some use cases.
I did not use any ACID compliant transactions with MySQL.
What do I think about the stability of the solution?
From my experience, MySQL was pretty stable.
What do I think about the scalability of the solution?
I know MySQL has been used in industries by a lot of companies, which means that it is scalable. That is the extent of my knowledge. It should be good because MySQL has been used by industries. I know Facebook uses it.
How are customer service and support?
I would rate the documentation and online support a 10 out of 10.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I do not deal with Oracle products anymore. That was just a one-time thing that I had for college.
Which other solutions did I evaluate?
Unfortunately, I do not deal with AWS, Google products, or Azure products because they are usually paid.
What other advice do I have?
MySQL is a very useful database which is used by a lot of companies, so it should be really good. I mostly dealt with MySQL in the last 12 months. My experience with MySQL overall was pretty good. I would rate this review a 10 out of 10.
