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.
It is used across the whole organization. The main business problem that it address is to serve as a database for our own and third party applications.
Pros
Great stabiltity
Good performance on retrieving data
Easy configuration
Easy management
Cons
DDL operations do not work well on running MariaDB Cluster
Cluster management from CLI could be improved
Likelihood to Recommend
If you use a MariaDB Cluster, it is well suited in scenarios where your tables don't change, because if you perform DDL operations on a running cluster, you will break it, so you must prepare a downtime window to perform this type of operations. If you don't need a cluster, I think MariaDB Platform works fine in almost every scenario.
VU
Verified User
Engineer in Information Technology (Information Technology & Services company, 51-200 employees)
My team is currently using MariaDB Enterprise to store data for several customer-facing microservices that delivery critical weather data in the form of alerts and reports. To the best of my knowledge we are the only team in our division that uses it. Previously we were using a NoSQL implementation but it was not a good fit for the types of data we store. Moving to a relational model has made a huge improvement in performance and reliability. We specifically chose MariaDB as it supports a multi-region replication model.
Pros
Replication - Works extremely well and has very reasonable latency.
Monitoring - There is no shortage of tools for monitoring clusters.
Reliability - Rock-solid product that appears to be quite resilient.
Cons
I honestly can't think of anything I'd change.
Likelihood to Recommend
Given that MariaDB is a relational database, it is best suited for situations where data integrity is a necessity and said data is highly structured. It is a little more difficult to scale so having a consistent load is also a plus since you can plan for capacity more easily.
If being able to scale easily and dynamically is import then MariaDB might not be a good fit. Also if data consistency is less important than speed or flexibility then there are other database models (document, key-value store, etc.) that may be a better fit.
VU
Verified User
Engineer in Information Technology (Information Technology & Services company, 10,001+ employees)
SQL - Is well known and supports most types of usage cases for a database.
Open source - means there's lots of support and resources to develop on.
Multi-platform - runs on any operating system and doesn't tie it down.
Cons
Full text searches - slows startup to the extreme, leaks memory, can be buggy.
Startup process needs to be streamlined and with more output. You shouldn't need to debug the system to find out what the startup process is doing.
More consideration to using multiple databases. Most solutions seem to concentrate on single database products.
MariaBackup is buggy and might not work on larger databases. Taking backups or restoring them takes manual work. Could really need some easy to use tools and less hand scripting shell scripts.
Likelihood to Recommend
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.
VU
Verified User
Engineer in Information Technology (Accounting company, 11-50 employees)
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)
It is the main data base solution for almost all the applications we are developing that require storing data in relational database. It's used for storing content and parts of websites as well as some configuration. It's also used for simple contest apps that require entry code checkout. Software development team is mainly working with MariaDB but apps, website or tools based on MariaDB are used across all organization.
Pros
It's easy to use for software development team members with knowledge of SQL.
It's better than standard mysql solutions, it's a little bit faster.
It's also often required for some applications that we use for example CMS.
Cons
While using with large data it's slowing.
Likelihood to Recommend
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.
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!