MariaDB Platform Reviews and Ratings

Use Cases and Deployment Scope

We use MariaDB whenever we need a database server compatible with MySQL Server, and do not wish to use Oracle MySQL Server. MariaDB largely has been an excellent choice, particularly when there are documented bugs with Oracle MySQL Server that prevent us from using it in a specific environment or application. Due to its branched codebase and rapid development cycle, MariaDB does not replicate various bugs or performance issues that MySQL Server can exhibit in specific scenarios.

Likelihood to Recommend

MariaDB is ideal when your environment or application is affected by specific MySQL Server bugs that are not being resolved any time soon, and you need a more or less drop in replacement. It is also the best solution when you have limited resource constraints - in my experience performance is improved in limited resource environments when using MariaDB as opposed to MySQL Server.

Use Cases and Deployment Scope

In a distributed application, on each host we have an instance of MariaDB Platform that collects data. Then every day the data is sent to a centralized server with another database. MariaDB Platform offers a great way to decentralize and to keep performances at top, including robustness and availability.

Likelihood to Recommend

Of course it depends on the use you need your application, the scenario. Ideal if for "little" applications, not "corporate" ones. So if you are evaluating SQL server VS MariaDB Platform go straight with MariaDB, opensource, easy to move/backup, fast response (with a limited number of users in the same time)

Use Cases and Deployment Scope

We have a MariaDb Cluster to store 2.2 TB of data with a manual sharding to optimize the access data. We use several engines like Spider, Connect, Federated, MyIsam, Memory and InnoDb. Currently, we are planning [to] add ColumnStore too. We also have a PoC with Galera for HA between managers and we did uses cases with Max Scale.

Likelihood to Recommend

<ul><li>Applications where the users need [to] execute many short queries.</li><li>With new storage engines such as Aria, which allows to replace MyISAM with some improvements, and XtraDB, which evolves InnoDB.</li><li>To fuse the legacy features with the features available in NoSQL databases.</li><li>Connection management, which allows multiplying the number of concurrent accesses.</li><li>New clustering engines, such as Galera, which allow interesting possibilities for Cloud adoption. </li></ul>

Use Cases and Deployment Scope

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.

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.

Use Cases and Deployment Scope

MariaDB is used for several in-house solutions with internal and customer visibility as well as a replica repository as the first stage of Analytic data. We use a combination of Galera and Primary Secondary with Maxscale as a load balancer and router. Currently, everything is on-prem but we are looking at migrating to the cloud.

Likelihood to Recommend

Different services, read-write split, replication are well suited. Write heavy with Galera Cluster presents challenges.

Use Cases and Deployment Scope

MariaDB is our production database for clients' VRP.

Likelihood to Recommend

<b>Well Suited</b>

For any relational data, one of the easiest databases to use

<b>Less appropriate

</b>Big Data is lacking.

Performance, manageability of data

Use Cases and Deployment Scope

MariaDB is our primary relational database. We have multiple databases including WordPress and Magento running on it.

Likelihood to Recommend

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

Use Cases and Deployment Scope

Initially we just use it as in place upgrade for MySQL as part of system regeneration, later it turned out that its performance was far better than the original MySQL that we replaced. Our system was designed to be low maintenance and less human interaction, therefore we need a database system that quite simple and practically maintenance-free.

Likelihood to Recommend

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

Use Cases and Deployment Scope

We are using MariaDB Enterprise 3-node cluster setup in production with 10.4.13 version and on top of the cluster using max scale router to load balance read/write OLTP traffic. In the 10.4 version, there is a lot of improvement done for InnoDB performance and especially the changes regarding the instance drop of any table fields. I also found very useful the use of the SQL-mode feature for strict typecasting.

Likelihood to Recommend

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

Use Cases and Deployment Scope

<div>We currently have 2 installations of MariaDB TX Cluster formed by 3 nodes each installation.

</div><div>One installation is in the pre-production environment and another is in the production environment.

</div><div>In MariaDB TX Cluster we have the databases of two of the main applications of the company, which in addition to having internal use also have public use from the internet.</div>

Likelihood to Recommend

<div>Our installation scenario is a MariaDB cluster composed of 3 nodes to achieve high availability in the service and in this way the application that accesses the backend (MariaDB) is always working and is not down at any time.

</div><div>To achieve high performance of the application when accessing the database, a MariaDB MaxScale has been mounted that acts as a proxy for queries to the database.

</div>