MariaDB Reviews

For a smaller company with fewer resources and less of an established investment in other database software (including having paid the substantial premium for staff expertise with that other software), MariaDB is an excellent idea. It's easier to learn, easier to manage, easier to license.

Support for technical issues we've encountered has been (IMO) excellent. Response on feature requests have been disappointing, not so much compared with other db vendors (who are worse), but with the quality of support we've received otherwise.

We aware that Oracle is half-heartedly developing MySQL, therefore an in-place upgrade to a database system that still supported & actively develop will be needed. For this scenario, MariaDB is fit perfectly.

Since it compatible with MySQL, most support material can be found easily on the net. For specific MariaDB issues also can be found easily since it widely used by people. So far we haven't encounter issue that requires us to contact the developer.

MariaDB is well suited when it comes to making any DDL changes or DML changes in DB objects.

So far my interaction with the MariaDB support team has been average. I would suggest MariaDB support to users in case they do not have enough experience in MySQL internal workings and management.

It's really good as a database for CMS, small apps. Its relational structure is well suited for organizing structured data used while building web apps and other web solutions.

It is noticeably slowing when working on tables with 10-20+ millions of rows. We had cases when we made operations, for example select or insert, on over 60 millions rows and some of them took a few seconds. It was crucial to use faster servers to achieve better latency.

Documentation of MariaDB is well written. We didn't need to use other support.

Having opened several support tickets with MariaDB Enterprise support I have been consistently pleased with their knowledge and responsiveness. Tickets were updated in a timely manner and every problem was found to have a solution. They were also able to offer useful feedback during our architecture and planning phases. They have been invaluable partners so far and we have no reason to think that will change moving forward.

MariaDB suits most use cases, but also needs expertise to use and debug. So if you haven't got experience in MariaDB/MySQL, some problem cases might be too difficult to solve without help.

MariaDB is well suited for running secure ACID-compliant relational databases with vertical scaling support.

MariaDB has a great community and well-written documentation. That makes troubleshooting is much easier.

MariaDB is more suited if you need to quickly launch a simple application or store simple data. Its simplicity to download, install, and upgrade is one of the main strength for us. However, for more complex use case that requires more out of the box solution or needs a high precision, I don't think MariaDB is suitable.

Since MariaDB is an open source software, there is no direct line support that we can use. However, it has a massive community and user base and there are countless documentation, forums, questions and answers in internet about MariaDB, so far we haven't had any problem that we can't get the answer from the internet.

MariaDB is an economical, scale-able, relational database.

Great support. Responds quickly to production issues. Sometimes they ask for a lot of information and it often takes me more time to gather all that they need than it does for them to actually resolve the issue.

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.

Well I have never had to use MariaDB for support. However, they get a ten because the support community online is just fantastic. There is always someone there to answer a question. Moreover it is easy to find documentation online. Again, this is often the case with open source software.

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.

Compared to other solutions (such as Oracle), there aren't quite as many professional support or documentation options available. However, MariaDB is widely used and there are a lot of online communities that share helpful information. Additionally, much of the existing MySQL documentation is still valid for MariaDB, and while some third-party applications officially require MySQL, many will also work seamlessly with MariaDB.

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.

Very good RDBMS, very similar to MySQL.

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.

MariaDB is very usable and stable to be used in production settings as an alternative to MySQL. The shortcomings of SQL are present but well understood in the community, and if the decision were to be made again, I would choose MariaDB over MySQL on future projects.

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.

On Debian Linux, it is recommended to install a MariaDB repository and retrieve the product from there. It is both a good and a bad thing: it is more up-to-date than Debian's version (as Debian tends to lag behind with stable software), but it also makes your packages drift away from the generic system.

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.