MariaDB Reviews

It's easy to use and open source. Currently, I use it more and more as it is easier than the other.

It's easy to set up.

The product is open-source.

I don't know what we want to improve about it, however, we don't use it for everything. We use it for specific projects. It can fit my project, and we don't know how we can use it more.

The performance could be a bit better.

They could make the solution stronger. It's not stronger than PostgreSQL, for example.

I've used the solution for two years. 

The stability is good for how we use it. We don't use the replication and cluster. We only really use the standalone server and that's it.

We don't use technical support. I cannot speak to their services. 

It's not overly complex to set up. Maybe when we set up matters like replication, it's a little complicated, however, it's pretty easy.

We only need one person to maintain the product.

We did not have the help of integrators or consultants. We installed the server and deployment did not take too much time. It was about 20 minutes or 30 minutes to deploy.

The solution is open-source, therefore, it has no license.

The product is easy to use and not hard to learn, therefore, when someone asks me for a good DB to use, then I tell them about MariaDB.

I'd rate the solution eight out of ten.

We use MariaDB for a crypto exchange. We are currently in a test environment.

The solution can improve by having support for more integration. However, at this time it is working well for us.

I have been using MariaDB for six months.

The stability of MariaDB is good, it has high availability.

MariaDB is scalable.

The DBA is enough for support for MariaDB at the moment. If we need more support, then they will contact the consultants.

We are using MySQL. We moved to MariaDB because we found out that it is better for the cloud environment.

MariaDB's initial setup is not complex. It's just straightforward. It took us one day to complete.

The implementation can be done via all DBA.

There is a monthly subscription to use MariaDB.

I rate MariaDB an eight out of ten.

Our primary use cases of this solution are for emails and all the functions you would expect from a server. MariaDB is deployed on-prem, on one of our Linux servers. 

A valuable feature is that we can use it for quite a few things, all the things you'd expect from a server—along the lines of Linux's Lightweight Directory. 

MariaDB could be improved by adding more automation. 

We have been using this solution for the past five years or so. 

This solution is stable. For deployment and maintenance, we have a team of four admins. 

This solution is scalable. There are about 100 people in my company using MariaDB. 

I didn't use a different solution before implementing MariaDB. 

It is very simple to install MariaDB. We did it ourselves and it took less than a day. 

We implemented through an in-house team. 

We pay for a yearly license. We don't currently have plans to increase the number of users in the foreseeable future, but we will do so if we need to. 

I didn't evaluate other options before choosing. 

I rate MariaDB an eight out of ten. I recommend this solution to others considering implementation. 

The solution is primarily used to store data and for our cloud platform backend database. I use the solution for many projects.

The solution's high availability is its most valuable aspect.

We have found the product to be stable. 

The initial setup is pretty simple. 

The stability could always continue to be improved upon.

I've been using the solution for three years. 

The solution is stable and the performance is good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

There are about 100 end-users in my organization that use this product.

I've never dealt directly with technical support. When there has been an issue, I tend to work to solve the problem myself. 

There is so much information available, you can easily just Google the problem and likely you are able to troubleshoot the problem yourself. It's easy to find what you need online. 

I found the initial setup to be very simple and straightforward. 

The deployment was quick. It maybe only took one hour. 

We have a DPA team that's able to deploy the solution. For my department, we have six people on it and they're able to handle both deployment and maintenance. 

The implementation was handled in-house. I did not need the assistance of an integrator or consultant. 

We don't use a license, however, it is possible to pay for a yearly license if necessary.

I'd rate the solution at a ten out of ten. I'm very happy with it overall. 

I would recommend the solution to others. It's easy to find details about the product online and to learn about it. 

Our clients have a variety of use cases. I'm not familiar with just one.

The solution is very easy to implement.

The product makes it very easy to use as a primary database or a standby database.

The switches are easy to use.

The initial setup is pretty fast.

The solution offers very good automatic features.

The GUI could be improved a bit. The user interface needs to be improved.

I haven't tested the latest version of the solution. There may have been updated and changes that I am not aware of.

The stability of the solution could be improved, as we've had issues.

It would be ideal if the solution could offer an active-active cluster.

We have been dealing with the solution for about one year. It hasn't been too long.

The stability of the solution isn't perfect. I personally have had some issues. It's something that they need to work on.

I've never really dealt with the scalability aspect of the solution. I'm not sure how it would handle the process. I've only tried the DR side, in order to have primary and standby.

I don't have any experience with technical support. I can't speak to how knowledgeable or responsive they are at this time.

The initial setup doesn't take too long. It's standalone, so it will maybe take one hour to install the machine. It's fairly straightforward, and not too complex. A company shouldn't have any issues with the setup.

You only really need two people for deployment and maintenance. YOu don't need a very big team to manage everything.

We are using the community version of the solution.

We implement the solution. We typically deal with on-premises deployments. We use the latest version of the solution.

Overall, I would rate the solution at an eight out of ten.

I'd recommend the solution. We've largely been happy with it so far.

We are using MariaDB for our federation of identity system, which is used to record students, service providers, and many other things. This system uses MariaDB as a database. 

We use MariaDB for identity provider services. Most of the things that we are doing are deployed in the container mode. All such solutions require a database, and MariaDB is easier to use for these kinds of deployments.

It would be good if they can maybe improve the mass import in the database. Currently, for importing a large number of data, we create a CSV file and upload all the things in the system. The system does not activate them by default. We have to do this manually. This may be due to the version we are using, but this is something we would like to see improved.

I have been using this solution for five years. 

It is stable. We have no issues.

It is scalable. We are a regional research and education network. MariaDB is a part of the tools that we have deployed to provide services for such institutions. Three other national research and education institutes are also using it, and all of these institutions have many campus users. So, a large number of users are using it, but they don't even know that it is MariaDB because they are just using the tool or the application that has MariaDB as backend. We do plan to increase its usage in the future.

We didn't contact them.

I won't say we switched because we still have another system running PostgreSQL. We started using MariaDB because we were using some tools for identity federation, and these tools come with MariaDB by default. We did not choose MariaDB as a standalone product. If we stop using any of these tools tomorrow, we may no longer use MariaDB.

The initial setup is very simple because we are using a container, which means that it is just a deployment. It is a part of the installation of other applications. 

We didn't have to install MariaDB as a standalone product. We installed an identity management system, which automatically requires MariaDB, and all these things are done through containers. It is very easy these days when you are using a container. Everything is straightforward. It is just a matter of calling and installing them.

The initial installation was done by a consultant. Since then, we have deployed many other instances of the same thing. It is the same container, and we keep on deploying it. We just change the configuration.

We have only one person for its deployment and maintenance. We have a network and system admin who deals with the installation for us. We are just using MariaDB behind our federation of identity system. So, we don't deal with it daily. When we want to connect a university or any university wants to join, we install the application that has MariaDB, and that's all.

I would definitely recommend this solution. It has worked very well for us so far. I have no complaints about it.

I would rate MariaDB a nine out of ten.

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.

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.