MariaDB Reviews

Our software development team uses MariaDB and other databases as the storage facility for some of our applications.

Initially, we liked this solution because it is a drop-in replacement for MySQL.

The most valuable feature is that it uses multiple cores, which is better than some of the other databases. When we have eight or sixteen cores, the utilization ratio is a bit higher than previous versions of MySQL. I think perhaps the enterprise version of MySQL may have better support, but the free version does not work as well as MariaDB. This is with the factory default settings.

Scalability is an area that needs to be improved.

When we have had issues with accidental computer shutdown or a power outage, our MariaDB database was corrupted. This did not happen with our Oracle or Microsoft SQL Server, so I think that there might be some differences in the database engine that better deals with these kinds of accidents.

We have been working with MariaDB for seven years, since 2013.

We have not experienced much in terms of instability. We have been running our instance since 2013 and it needs almost no maintenance. You just install it and forget it. It's that easy.

MariaDB works with just a little configuration for a small dataset, but it does not scale as well as Oracle of Microsoft SQL Server in our applications. For example, additional manual configuration or tweaks are needed so that a query will return in a reasonable time when there is a high volume of records.

Our client has between 10 and 30 concurrent users.

Getting proper support is sometimes difficult because when you have a technical issue and use Google to try and find a solution, there will be millions of results. You have to tackle it by yourself but even if there is the same error message, you can try every posted solution and it still might not work. There is not a single source of truth that you can rely on.

The initial setup is straightforward and I think that the installation can be completed in a couple of minutes.

We have our own team for deployment and maintenance.

I think that for a small team of fewer than ten people, such as a couple of developers, MariaDB is a very easy start. When the team size grows or when the complexity of the application grows, you might need to try other options such as Ingres or MySQL. In our case, at the very beginning, MariaDB covered almost every technical requirement for releasing version one of our application.

It is definitely a good start. Once the product has grown to a point where the developers know in which aspect MariaDB does not fulfill the requirements, then it's time to find a better match.

At this point, I cannot think of any additional features that I would like to see because most of what I want is already on the roadmap. I think that they plan to implement them one by one.

I would rate this solution an eight out of ten.

My experience is not at the technical level, it's in the basic areas. My role regarding MariaDB is from the procurement and the technical deployment perspective.

The primary use case of MariaDB is for the payroll solution, for the Columnar queries, and for the general information query on the database.

From the user's perspective, the performance of the columnar queries is very good in terms of the database when comparing it to the Oracle, and MySQL.

The scaling for database online transactions needs improvement. Our users now are restoring the data. They should explore the performance of online transactions.

It's performing well and is meeting our expectations. 

The need for technical support is minimal because it is simple and you can do your own troubleshooting with the help of the documents that are available.

The deployment is simple, there are no conflicts.

We deployed MariaDB within a day.

To run a 24/7 operation we need at least five team members on the database administration side.

The licensing cost is approximately $4000.00 per year and the licensing is based on the software and the number of posts that you make. 

MariaDB is the solution that was finalized when looking and comparing it with Oracle and MySQL. MariaDB has an advantage due to the columnar queries and data retrieval.

If you require the use of columnar queries then you should be using MariaDB.

Our usage is very limited and we don't know all of the features and how they function.

I would rate this solution an eight out of ten, as I have not yet explored all of the functions. 

We are not using MariaDB alone, it is being used with other applications such as ServiceNow.

We are focusing on the underlying database of ServiceNow. 

We provide our customers with complete solutions that include implementation, support, and training.

Currently, our customers are on-premises and they have not yet considered this solution for on cloud deployment.

This solution is user-friendly. It's easy, and similar to MySQL.

Some areas where this product could be improved are in the clustering technologies, redundancy, active-active deployment model, and also monitoring the backup and restore solution to the cloud.

They have made some enhancements on the product but I think that scalability and redundancies are a concern for the entire team. In the next release, I would like to see improvements in the scalability and redundancy features.

This solution is stable.

This solution is scalable.

It is not suitable for mission-critical applications, but it is stable for other applications.

We had a customer who was fronting MariaDB with ServiceNow and we were not able to help her with a specific situation. We contacted customer service technical support and they were very good. They were able to solve our issue in a short time.

The initial setup is easy and straightforward.

The deployment took a day.

We are resellers but we are willing to be partners with MariaDB.

Before starting with the implementation and deployment you should read the guide.

You should look at the suggested tips, tricks, clues, and the requirements to avoid having any problems.

I would rate this solution a nine out of ten.

We are a software and service provider and we have a lot of customers who are using our platform on the backend, which includes MariaDB. Our platform is for cloud telephony and the interface is the PHP Laravel Apache Platform. We have a hosted PBX platform and we are using Asterix as a telephony server. MariaDB is the database part of the solution.

MariaDB performs well as the backend database for our cloud-based telephony solution.

With respect to clustering and the master-slave configuration, sometimes the slave goes out of synch. If one server goes down then the other server in the cluster should be able to handle the load. If the synchronization were better and it was easier to maintain the cluster then that would be an improvement.

I have been using MariaDB for almost five years.

The stability is good, although in clustering, with the master-slave configuration, sometimes the slave goes out of synch. To that extent, stability becomes a challenge and is impacted because we want both the master and slave to be in-synch.

We have a lot of customers who are using our platform on the backend. Also, there are a lot of customers using our telephony product on the front end.

We have five or six clusters and as our business grows, we plan to use it more intensely.

We have our own technical team and to this point, we have not subscribed to receive technical support. However, we are thinking of taking it now because sometimes we have difficulties. There are a number of companies who do provide technical support.

The installation is straightforward, but depending on how efficient you want to make it, it can become complex. You have to have a good level of experience to be able to use it. Otherwise, there can be problems and you won't be able to handle it.

My technical teams, including the development and instructure teams, were responsible for the deployment.

This is an open-source product, which can be used free of charge.

We have not compared this product to many others. 

Our use of MariaDB is very basic, so it's a good platform compared to many others.

As it is a good product, I can recommend it to any users. If you want to have paid versions then there is Oracle and Microsoft SQL, but MariaDB is quite good and unless you have some specialized requirements, of which I don't know what they could be, you can use mariaDB.

I would rate this solution a seven out of ten.

We are a solution provider and MariaDB is part of an offering that we deploy for our customers.

What I like best about MariaDB is that it is open-source and reliable.

Master-master replication is something that needs to be simplified.

I would like to see support for deploying MariaDB as an embedded database.

I have been using MariaDB for three years.

This is a reliable product.

Scalability is not an issue with MariaDB. We have deployed it to lots of our customers.

I have been using the Community Edition that does not come with support, but the documentation is great. Enterprise support is available for those who are using a licensed version.

Prior to MariaDB, I was using MySQL. After it was taken over by Oracle, we made the shift to MariaDB.

The initial setup is straightforward and it takes approximately half an hour to deploy.

I handle the deployment for this solution myself.

I used the open-source version, which is available free of charge.

This is a good product and I absolutely recommend it.

I would rate this solution a ten out of ten.

When I worked for Groupon in Korea, the main production database was MariaDB. We used it for eCommerce. It was a database where we stored data.

I would like to see more compatibility going forward. This would help if there is a need to change databases. E.g., if I change from MySQL 5.7 to another database, then MySQL could be the master database and this could database could be the slave. The replication capability is very important.

Two years.

I have not contacted the technical support. We haven't needed it.

We have recently upgraded to change our database and our production database is now MySQL 5.7. If someone wants to use memory based data, then MySQL is better than MariaDB.

We are using MySQL but MariaDB can solve things better than MySQL. Maria DB has better performance than MySQL.

Sometimes Percona is better.

MariaBD is good. It is almost perfect. I would recommend it.

I would rate this product as a nine (out of 10).

It is very easy to develop with MariaDB.

The performance is very good.

It would be helpful if I could specify multiple drives for the database storage. That is not supported by MariaDB. For example, in Microsoft SQL Server, you can have storage on multiple drives.

I have been using MariaDB since 2014, between five and six years ago.

MariaDB is very stable. We have used it with perhaps 40,000 concurrent users and it is never down.

The scalability is something that can be improved.

In my previous organization, we had five developers using it.

I have not been in contact with technical support because the performance is very good and we haven't had any problems that necessitated contacting them. The documentation and community support is very good, which is probably why we didn't have any significant problems.

I have also used Microsoft SQL Server.

The initial setup is straightforward and the deployment can be done in minutes.

This is a product that I would recommend.

I would rate this solution an eight out of ten.

The primary use case is for merging reports, merging agents, and we have implemented for business intelligence.

The most valuable feature is that it is a database.

Performance with databases is always the same, we always want more.

Stability needs to be improved. If you are creating a class test, modern machinery or working with the databases, it's always a little bit difficult to configure and keep everything working.

The addition of a workbench for managing this solution would be an improvement.

Also, some kind of technical support to help in getting better performance.

We have been working with MariaDB for ten years.

It's not very stable. It needs improvement.

We have never used the technical support.

Previously we worked with MySQL.

The initial setup is straightforward for our development environment, but for our production environment, the requirements are more. There is more work to be done, such as indexing and similar things.

The deployment for the development environment takes only ten to fifteen minutes.

It's an open-source solution.

I am an IT engineer. I am always researching the best solutions for our clients.

I work mainly with open-source solutions, such as Liferay and WordPress.

Before this product was called MariaDB it was called MySQL.

I would say that for most use cases it works fine. 

Before implementing you have to understand what your use case is for.

Other databases work better for different use cases. You have to ask yourself if you want to use a relational database or a NoSQL.

I would rate this solution an eight out of ten.