TrustRadius Insights for MariaDB Platform are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
High Availability: Many users have praised MariaDB TX Cluster for providing high availability, which is crucial for their business needs. This feature ensures that their databases are always accessible and minimizes downtime.
Performance Improvement: Several reviewers have mentioned the great advantage of using the proxy for MariaDB, MaxScale, as it significantly improves performance. Users appreciate the faster response times and enhanced efficiency they experience when using this feature.
Quick and Helpful Support: The prompt and helpful support provided by the MariaDB team has been highly appreciated by many users. They have stated that their questions were answered quickly and efficiently, making it easier for them to resolve any issues they encountered.
We use MariaDB for all of our customer-facing applications. It provides replicated data across multiple sites without the high costs of many other DB solutions. It delivers great performance at a great price with flexible engines that allow tuning based on the needs of your data and applications. Their support is fast and thorough.
Pros
Query optimization
Table partitioning
Relational and non-relational data
Cons
Adding servers to replication series (playing catchup)
Likelihood to Recommend
MariaDB is an economical, scale-able, relational database.
VU
Verified User
Director in Engineering (Information Technology & Services company, 51-200 employees)
MariaDB is being used across our entire organization for various databases. Various different teams use MariaDB and rely on it to maintain their backend application. We implement monitoring and metrics for MariaDB to ensure we are getting the best performance out of our databases. MariaDB can be replicated on other servers for high availability
Pros
Stores data
Backwards compatible with MySQL
Opensource
Simple to setup
Easy query language
Cons
Query language doesn’t support working with arrays.
Doesn’t support full outer joins.
Not guaranteed to be 100% compatible with MySQL.
Likelihood to Recommend
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.
VU
Verified User
Engineer in Engineering (Internet company, 51-200 employees)
Vital db for quite a large number of our applications used internally and externally. The database is used for some management tools used by the infrastructure team. Externally it's being used for reporting to our customers as well as holding some of the metadata. MariaDB is tied into Galera which also helps out considerably for high availability.
Pros
Fast writes. Writes are fast, where it depends on the hardware.
Reads are fast. Putting into memory is easy.
Functions and procedures are easy to implement.
Paritioning is nicely implemented.
Cons
Bloating. Can't reduce the size of idx log file, especially when data is truncated from tables. Space is not reclaimed. Need to find way to "shrink" file.
Writes are dependent on hardware. If hardware isn't great, writes will be effected. If that can still be solved through software.
Flushing of cache data is not as fast as it should be. There can be cases of malformed data.
Likelihood to Recommend
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.
I use MariaDB for monitoring solutions and an open source project. It's easy to use and I can always find great support. I also have it in a replicated scenario so if something were to happen then I have a backup. This is a great product and would definitely recommend it for someone trying to learn new things!
The Engineering department uses MariaDB for its OLTP system. It solves the problem we had with NoSQL databases to give us an ACID compliant reliable database storage engine.
Pros
Gives us the flexibility to design data structures which can be joined to give data served by our APIs.
Provides us options to use multiple storage engines based on the data being stored.
Cons
Replication technology can definitely improve. Currently we face lot of issues with replication causing table locks.
Provide better troubleshooting tools out of the box, for example a comprehensive GUI like SSMS for SQL Server.
Alter table and add indexing is an overhead on large tables which causes replication and storage issues.
Likelihood to Recommend
Well suited for medium scale read and write systems
Not suited for systems where write workloads are high and require multiple masters to support the volume
VU
Verified User
Engineer in Engineering (Internet company, 501-1000 employees)
We use MariaDB as a drop-in replacement for MySQL. We benefit from the fact that it does not require changing the client side at all - we maintain some legacy applications that would not be easy (or even possible!) to change. At the same time, we benefit from the performance and stability upgrades that MariaDB offers over MySQL.
Pros
The primary reason for me to migrate from MySQL to MariaDB was its stability. I experience more than one crash with data corruption on MySQL's standard MyISAM and InnoDB; I haven't seen any with MariaDB.
I love progress reporting for ALTER TABLE queries. In MySQL you would be facing a long running ALTER TABLE query and have no way to know when it finishes. With MariaDB you see the progress in the process list (especially important if there's a boss breathing down your neck!)
I haven't done significant benchmarks, but MariaDB seems faster than MySQL. I think it is mostly evident when using subqueries.
Cons
MariaDB has added a lot of extra features over MySQL. However, I think one in particular is still missing - and really, just the one - an ability to compute median values from the data. I miss it in my work quite often.
Likelihood to Recommend
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.
