MySQL--Great RDBMS for non-huge DB needs
April 12, 2021

MySQL--Great RDBMS for non-huge DB needs

Yaniv Vararu | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with MySQL

MySQL is serving more than one department in our organization. In the R&D department, it's being used as part of our software development. Other departments such as product, customer success, support, business development, and more are using it for managing the customers, for getting analytics, for creating reports and dashboards, and acting by this data.
  • Since MySQL is open source, it is free to use under the GNU license
  • Before any update to data, it pops up a summary for approval, which lowers the risk of making a mistake
  • Performance is great if you need a relatively small DB
  • Compatible with many operating systems and integrates with many development tools
  • If you need a big/huge RDBMS, MySQL is probably not for you (performance-wise)
  • Complex joins/transaction handling causes temp hangs and performance issues--this can be improved
  • Fine tuning is not that easy--you'll probably need an expert (in-house or outsourced) for it
I used these RDBMS in the past in previous companies. In the company I currently work at, we used MySQL from day one. The main benefit over Microsoft's SQL server is that MySQL is free to use (GNU) which makes it easier for startups in their early days when trying to minimize costs.

Do you think MySQL delivers good value for the price?


Are you happy with MySQL's feature set?


Did MySQL live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of MySQL go as expected?


Would you buy MySQL again?


MySQL is best suited for us in managing our customers' definitions, accounts' structures, configurations, etc.--anything that is being set up once and updated only once in a while (and grown at low scales). The data of our customers' actions in the system is not saved in the MySQL DB since this changes in real time every second and this type of DB is less suited for so much data and such frequent changes.