MYSQL
Use Cases and Deployment Scope
test
Pros
- test
Cons
- test
Likelihood to Recommend
test

Ease of Use: Users have found MySQL easy to get started with, lightweight, scalable, and well-supported. They appreciate its quick processing speed and flexibility in handling various tasks efficiently. The open-source licensing adds to its appeal by offering a cost-effective solution for diverse database needs.
Reliability: Reviewers acknowledge the proven reliability of MySQL over time, providing a stable foundation for their data management needs. The consistent updates and enhancements contribute to its reputation for dependability. Users trust MySQL for critical operations due to its track record of performance and stability.
Support and Resources: Customers value the accessible technical support provided for MySQL, along with the abundance of online resources available. The cost-effectiveness of using MySQL is also highlighted as a significant advantage by users. With widespread knowledge about MySQL across communities, users can easily find solutions and guidance when needed.
test
test
We use MySQL mostly for relational data base system for our core data base related work. It work as a tool for storing structured data and many web services dependency on MySQL for retrieval and storage.Business problems we solve using MySQL includes data management and reporting ,Data warehousing and analytics.
MySQL is best suited for applications on platform like high-traffic content-driven websites, small-scale web apps, data warehouses which regards light analytical workloads. However its less suited for areas like enterprise data warehouse, OLAP cubes, large-scale reporting, applications requiring flexible or semi-structured data like event logging systems, product configurations, dynamic forms.
We use the MySQL database for applications like Confluence, Jira, and a few other Java-based applications. As it is Open source, we have also been using it for application development and testing purposes.
MySQL is a very lightweight database, which makes it faster and easier to manage and our applications run smoothly on the MySQL database.
In my experience, the MySQL database is well-suited for the development and testing of small-scale applications. The database is easy to configure and doesn't require much maintenance, so it can be handled by a few DBA resources.
However, I think MySQL is not suitable for large datasets and OLTP because of scalability challenges.
MySQL is being used for a few projects in our organization for storing master data used in the applications. MySQL is easy to learn and use for delivering high performance and also supports scalability based on the requirements.
We are using MySQL in all the environments including Development and Production environments. It is cost effective to use MySQL as it is open source product.
MySQL is ideal for small to mid-size organizations where data volumes are not too high. Being an open source product, it can help to save cost associated with acquiring licensed products. It is not recommended for large organizations as managing large volumes of data using MySQL will not be easy and large volumes of storage, memory and processing will be required with increase in data volumes.
It is solving the problem of efficient processing of a decent amount of data sets. Before that, all data was stored in an Excel sheet, which was difficult to manage, and the configuration system froze during processing. However, with the advent of RDBMS, it solves a very critical problem for us.
If you are looking for a database management system which is easy to use then MySQL should be the number one choice without a doubt, however, if you are looking a platform to handle large datasets and complex queries then you might have to give it a thought.
We use MySql to store our long time storage data and a backup place for our opensearch indexes so if any index is corrupted or delted we can easily use the backup from he db and also we use it as a single source of truth for all of our operations and data and stuff
From me as a long-term storage user perspective it's good, it's not good if you need lighting fast response time it's just not made for it u can use other NoSQL databases but for relational i think MySQL is the most newbie-friendly database in the market
We use MySQL primarily for the backend database to our corporate intranet. In this case, it powers all the apps that run on this web-based system, including user details (matched against and extending our ldap directory), technical document retrieval, IT helpdesk tickets, and our design change request system.
MySQL allows us to implement an enterprise-grade database in a cost-effective and easily supportable way - we don't have to depend upon proprietary database formats, it has great performance, scales as we need it to, runs on a variety of operating systems, can be easily migrated to new hardware and is easy to securely backup.
Because it is easily and widely connected to, we can also use it in a variety of other apps and as a repository for large amounts of structured data.
From my own perspective and the tasks that I perform on a daily basis, MySQL is perfect. It has a reasonable footprint, is fast enough and offers the security and flexibility I need.
Everyone has their preferred applications and, no doubt, for larger data warehouses or more intensive applications, MySQL may have its limits, but for the area that I operate in, it's a great match.
We have at least 15 databases with MySQL We have solved our performance and response issues by getting queries fast
It is a profiling tool for queries that shows information about where MySQL spends time on query, its performance and response problems by getting queries fast and takes up less disk space,
We have deployed in house MySQL cluster for our fintech application where transaction flow is around 100 read and write transactions per minute. Cluster comprises of "Master Master and Slave" structure. Masters were used to Write and Read transactions and read only slave is usually used for data dumps. Also we have a Proxy in place to load balance between DB servers.
Scenarios where I wouldn't recommend MySQL:
*) If you have huge databases, in that case MySQL tends to get slow.
Scenarios where I would recommend MySQL:
*) If you have a medium size DB.
*) Need cost effective RDBMS solution
I use MySQL as a storage database in the context of machine log parsing and analysis. We have integrations between MySQL and our SIEM tool that allows us to store data in MySQL, but also access via our SIEM software for further in depth analysis. We store data across data of tables in MySQL for efficient organization and quick access.
The primary scenario I would not recommend MySQL is in the case of very large databases. It is commonly known that performance is lacking in this regard. Though it is well suited to those databases in the small to medium range. I would highly recommend MySQL when integrating with other software tools. Many tools, such as Tableau, have connectors that are ready to run and hook into your MySQL database. This makes accessing the data a breeze and is very helpful when integrating with other tools.