Is MariaDB better than MySQL?

Started by kathylewiss, Mar 31, 2023, 03:39 AM

Previous topic - Next topic

kathylewissTopic starter

Is there any reason to use MySQL nowadays? Are there any special features that make MySQL preferable in certain situations over MariaDB, MongoDB, or Percona?


MySQL lacks several features that are present in MariaDB, such as time versioning, support for OLAP and KVS engines, new data access and processing methods, compatibility with pl/sql Oracle syntax, and plugable custom data types. On the other hand, MySQL has its own distinct features, including a data dictionary instead of .frm files and metadata in myisam tables.

While MySQL supports operator syntax for JSON according to the standard, the advertised atomic DDL is not entirely true, as the database will not roll back a worn column with an ALTER TABLE DROP COLUMN.

If the additional features are important to you, then MySQL would be the preferred choice. However, if performance is the key consideration, then MariaDB may be more suitable. It's worth noting that Oracle has decided to abandon the feature freeze system after the release became GA, and they have introduced behavior-changing features.

As for Percona, while they used to have cool tooling and a team of hackers familiar with the core code of DBMS, their focus has shifted towards becoming a support business. Consequently, betting on them may not be the wisest decision at this point.

In my opinion, when selecting a database management system, it is crucial to thoroughly evaluate the available features, performance, and reliability to ensure the best fit for your specific project requirements.


MongoDB is not something I would consider, as it belongs to a different category altogether.

When contemplating between MySQL, MariaDB, Percona, AWS Aurora, and other options, there are several factors to consider. Firstly, it's important to determine if we have any interest in additional components beyond the core product, such as clusters or commercial plugins. Secondly, we should assess whether non-standard storage engines are necessary for our specific requirements. Lastly, we need to evaluate if business support is a crucial aspect.

Taking these factors into account can help us analyze and make an informed selection.

Alternatively, one can also choose to stick with what is provided within the distribution as a simpler option.

carefully weigh the pros and cons of each database option and consider factors like scalability, performance, reliability, and community support when making a decision.


Is it acceptable that they are essentially the same thing?

However, between the two options presented, I would opt for MySQL due to the fact that it is developed and backed by a corporation, as opposed to being solely reliant on a free community (which sets them apart).

In my experience with MariaDB 10, I encountered an issue pertaining to caching requests, even with the utilization of SQL_NO_CACHE. Removing the cache entirely seemed extreme, so I decided to revert back to using MySQL.

considering the origins and development process of different database management systems, it is crucial to thoroughly test and evaluate their performance, stability, and compatibility with your specific use case. Keeping an eye on potential issues and being open to switching between systems when necessary can help ensure optimal results in your database operations.


MySQL still remains a popular choice for many use cases due to its stability, robustness, and wide adoption. Some reasons why MySQL might be preferable in certain situations over other databases include:

1. Legacy Systems: Many organizations have been using MySQL for a long time and have established expertise and familiarity with it. Migrating to a different database system may not be feasible or cost-effective.

2. Application Ecosystem: If an application is tightly integrated with MySQL-specific features or uses libraries that are optimized for MySQL, it may be impractical to switch to a different database without significant rework.

3. Specific Features: While MariaDB and Percona offer compatible features and often enhanced performance, some specific features in MySQL might be better suited for particular use cases. For example, the implementation of certain replication methods or specific storage engines could be better supported in MySQL.

4. Vendor Support: MySQL is backed by Oracle, which provides enterprise-level support, certifications, and additional features that may be required in certain industries or for compliance reasons.

On the other hand, modern applications with high scalability requirements, unstructured data handling, or complex data relationships might benefit from using MongoDB or other NoSQL databases. Additionally, MariaDB and Percona offer improved performance, compatibility, and some additional features compared to MySQL, making them strong contenders for many use cases.

In addition to the previous points, MySQL continues to be a strong contender in the database landscape due to the following reasons:

1. Community and Support: MySQL has a large and active community, which means that it's easier to find resources, tutorials, and troubleshooting help. This can be invaluable for developers and organizations looking for community-driven solutions and best practices.

2. Enterprise Features: MySQL offers a range of enterprise-grade features such as advanced security options, online backup and restore capabilities, and support for high availability through features like Group Replication and InnoDB Cluster.

3. Familiarity and Skill Set: Many developers and database administrators have expertise in MySQL, making it easier to find talent and maintain existing systems. This can be a significant factor when considering the cost and effort required for training or hiring personnel with expertise in alternative databases.

4. Ecosystem Integration: MySQL has strong integrations with popular frameworks, ORMs (Object-Relational Mapping tools), and other tools in the software development ecosystem, making it a convenient choice for developers building modern applications.

The question of whether MariaDB is better than MySQL is subjective and depends on specific use cases, requirements, and preferences. Both MariaDB and MySQL have their own strengths and weaknesses, so the decision of which one is "better" depends on the context in which they are being used.

MariaDB is a fork of MySQL, created by the original developers of MySQL. It aims to be a drop-in replacement for MySQL, providing enhanced performance, additional features, and compatibility with MySQL. Some reasons why one might consider MariaDB over MySQL include:

1. Performance: In some benchmarks and real-world scenarios, MariaDB has demonstrated improved performance compared to MySQL, particularly in high-concurrency situations and complex queries.

2. Additional Features: MariaDB offers some features not available in MySQL, such as the Aria storage engine, thread pool, and additional data types. These features may be valuable for certain use cases.

3. Security: Both MariaDB and MySQL focus on security, but MariaDB has introduced some security enhancements such as the ability to enable encryption for different storage engines.

4. Open Source Commitment: MariaDB has a strong commitment to open source principles and is developed in a more community-oriented manner compared to MySQL, which is now owned by Oracle.

However, MySQL also has its own advantages, including a longer history, wider adoption, strong enterprise support, and a track record of stability and reliability. Additionally, MySQL may have specific features, extensions, or integrations that are not available in MariaDB.