MariaDB Reviews

If you need a robust and scalable OLTP rdbms, MariaDB works. If you need an OLAP, MariaDB is not for you. Look elsewhere. If you implement Galera, then you'll have a high availability database engine. No one true master, all masterless/slaveless. If you need to use a DB for management tools like Cloudera, etc... then MariaDB works.

MariaDB works well in a web development environment using PHP or Python. We have also used it in a Tomcat environment. I do not see any reason to use any other database such as Oracle, Informix, or any MySQL server. In my opinion they all under perform MariaDB when it comes to performance and ease of administration. MariaDB is very scalable. You can use the same instance for small projects with a few hundred rows or with a few million. MariaDB is powerful and that power can be found in its command line which makes the manipulation of any data easy, especially when the SQL is not of a proprietary nature.

MariaDB is especially helpful for organizations that are currently using MySQL but would like to move to a product with friendlier licensing terms. This is easier to do if you have an in-house programming team that can implement integrations on their own, as some outside firms will sometimes prefer to work with other database solutions that have more restrictive/expensive licensing.

Very good for a cheap and quick RDBMS solution an on an open system, it should fit most people's needs. However, I still would not put mission-critical applications on it yet.

MariaDB is best for use cases where MySQL was previously being used but due to licensing or not wanting to use Oracle's MySQL, you can use MariaDB. For the most part, it's a drop in replacement supporting the same syntax as MySQL, requiring no changes in applications which use it, meaning MySQL Databases can be migrated to MariaDB.

Easy to switch from another database. Installation is very easy and integration team always prefers to solve issues using MariaDB tool.

MariaDB is well suited in scenarios where it is possible to use open source software and scenarios that demands active-active clusters. MariaDB is maintained to date with the latest version of MySQL and will work just like MySQL. All the commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB. There is no need to convert the databases to switch to MariaDB. But in critical systems we do not risk using it yet.

[It's a] multi-server open-source application.

MariaDB is well suited for general purpose RDBMS needs or anywhere you need a DB that's simple to set up. For example, it is a breeze to use in Docker containers.

Originally Maria DB was recommended to me by a colleague as a stronger offering than the product I was utilising at the time, MySQL. My understanding is that the aim of MariaDB is to take market share away from MySQL. To answer the question directly Maria DB is very well suited in doing this operation of offering a solution from MySQL predominantly down to the similarities in syntax structure.

You can use standard MySQL client side libraries to connect to MariaDB servers, however, there is one caveat: MariaDB versioning. MariaDB is now at version 10, whereas MySQL is at version 5. If the client side has hardcoded version numbers it may behave in unexpected ways as it will see mismatching versions and especially one that it does not even know about.

Overall, MariaDB is a very good drop-in replacement for MySQL, as long as your client-side does not do anything fancy.

I use it instead of MySQL everywhere.

MariaDB suits perfectly if you want to switch away from Oracle-owned MySQL but still want to keep maximum compatibility and minimize efforts required for migration. It's also a perfect choice for any use case where usage of a relational database has been decided. However if for some reason you need enterprise-level support for your database solution, the choice for MariaDB might need some more thought since it's entirely community-driven.