MySQL Reviews and Ratings

Use Cases and Deployment Scope

We use MySQL to run the database back end of our company websites and a handful of OLTP applications. It provides a lightweight relational database system that is easy to manage and low in cost. Because we use the free version, support can be iffy, but, generally, it just runs without issue.

Likelihood to Recommend

<div>High read/low write applications such as websites is where MySQL's ease of setup and general usage really shine. It is open source and coupled with it's cross-platform availability allowing it to run on Linux makes for an extremely low-cost RDBMS solution.</div><div>

</div><div>Larger companies with higher budgets may want to look at more enterprise level solutions (SQL Server, Oracle, etc...) for larger OLTP and OLAP workloads for their scalability and support.</div>

Use Cases and Deployment Scope

Our proprietary CRM software uses MySQL as one of the databases. Its relational capabilities allow us to maintain data coherently even on a large scale, and making it possible to create the complex representation that is a customer and all the relative data about addresses, billing, preferences and so on.

Likelihood to Recommend

Applications requiring persistent data that need to be related to other data are a perfect use cases for MySQL. On the other hand, when the amount of data is really high, and the "relation" or connected data is not always the same, or when the relations are not so strict, then other databases would be better suited.

Use Cases and Deployment Scope

MYSQL is used as a backend database for multiple inhouse products . Its used to store data ranging from 5 G to 2TB in multiple environments such as DEV ,QA and staging . It can easily handle any amount of data and processes it very fast . We also use to test some security related items .

Likelihood to Recommend

It can be used for applications were the number of concurrent users are less or there is separation of schemas so that there is no database contention. It can handle large datasets but how big it can be , is a question mark , there were scenarios this can be less suited for Analytical workloads

Use Cases and Deployment Scope

I use MySQL to manage our customer data within our applications. This also allows me to easily query this data to check usage, spot trends, and confirm client issues when they contact us. Since it's ubiquitous within the SaaS realm, it's easy to find tools that can visualize MySQL data.

Likelihood to Recommend

It's great for querying large amounts of data. If you're running a very basic application, it might not be the best option.

Use Cases and Deployment Scope

MySQL is important to critical aspect of my organizations software product experience. It helps us with transaction management, account data management , know your customer verification documentations and auditing trails etc

Overall, MySQLas our RDBMS of choice for key applications goes beyond merely being a backend infrastructure tool, it helps shape a trustworthy and reliable experience for users of our products.

Likelihood to Recommend

MySQL performs well with applications that require security of data which is critical for a finance organization like mine. For example, a core part of our backend infrastructure is built on MySQL, because of its strong ACID ( atomicity, consistency , isolation and durability ) compliance . Its InnoDB engine ensures that user initiated actions on our applications either finish or do not happen at all and this is very important for a platform like ours where people initiate financial transactions.

For scenarios where MySQL is not appropriate, I wouldn't recommend it for analytics-heavy applications or tasks because these require full table scans, which is not a strong part of MySQL and usually will lead to a halt of other concurrent workloads.

Use Cases and Deployment Scope

I use MySQL as a core relational database management system to support a variety of business-critical applications. We leverage MySQL for both internal and customer-facing systems, including web applications, reporting dashboards, content management systems, and data pipelines. Its reliability, performance, and open-source nature make it a strong fit for many of our workloads.

Likelihood to Recommend

Dynamic web site.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

For a customer onboarding web application, we have used MySQL database. For web application MySQL database had been preferred choice in the past which provides both open source and licensed feature. Among other reason MySQL DB is easy to setup , simpler feature set, fewer advanced features, but lightweight, stable, and fast for read-heavy workloads.

Likelihood to Recommend

MySQL Database has been well suited for our web based

application used for customer onboarding. It efficiently handles data storage,

retrieval, and management of customer onboarding. So good for lightweight

application, with moderate for performance requirement and cost efficient solution.

MySQL database cannot be the replacement of large scale enterprise

database. Oracle database, MSSQL or Postgres would be go to option. Another

reason could be MySQL does not support many modern extensions/features like NoSQL

support, JSON data type, limited support for modern and complex SQL query

features.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.