MariaDB Reviews

I develop applications in my spare time. So, if the application requires a database, I use MariaDB by default.

It works fine. It's easy to set up. 

There is room for improvement in terms of security. 

I have been using MariaDB since 2016. I started using it when I was in school. Moreover, I use the latest version available, depending on what I am doing.

It is a very stable solution. I made a deployment for an internal IT service at one of the places I worked, and it's been seven years now, and it's still working perfectly. 

I would rate the stability a solid nine out of ten. There is always room for improvement. Nothing is perfect, and maybe there are some issues that I'm not aware of.

MariaDB is mainly a back-end application, so anyone using our service also uses the database. For example, if you use my monitoring service, which is used to monitor devices and appliances, then you'll be using the database. So, I'm not sure if that counts, but it's being extensively used in our company, and it's very helpful.

We plan to increase our usage of MariaDB in the future.

I have never contacted the customer service and support team because our deployment is not very big; it's just something small. The data contained in it is not considered a big deal by my supervisor, so there hasn't been a need to contact tech support.

Moreover, we haven't faced any issues so far. It's been working smoothly for us.

The initial setup is very straightforward. Mostly, I use MariaDB with Docker, so it's quite easy to set up and deploy. The documentation is also easy to understand and follow.

I usually handle the deployment myself, without the need for any third-party help. I followed the documentation and steps provided. MariaDB can be deployed in-house, but mostly it's self-hosted, and I use it with Linux. I mostly use the package manager version or the bundle I get from the website and apply it myself. 

I haven't used the licensing model for MariaDB, but I would prefer to use it since I am familiar with the platform and find it easy to work with. I wouldn't want to switch to a different database management system.

I've used PostgreSQL before, but that was in a personal capacity just for my own personal projects. Using MariaDB depends on the application I'm trying to deploy or what I'm trying to use. That's what determines if I will use MariaDB or Postgres as SQL.

If I am teaching somebody to program and write applications, I usually use MariaDB by default because it's open source, pretty available, and overall, I would rate MariaDB a ten out of ten.

But if I want to do a major deployment, I would have to get support. It's very stable. For example, I was using it to host a monitoring system, and it's been stable for a very long time. I haven't upgraded it yet, but it's working fine. It's been seven years since I did the last deployment, and it's still fine. 

We develop financial software such as credit management solutions for banks, financial institutions, and telcos, basically anyone who deals with credit. We are users of this product and resell to our customers. I'm the operations manager. 

The solution is valuable because it has PL/SQL compatibility. Our base was previously on Oracle and we wanted to change our solution to a DBS which meant finding something compatible with that language. It's really a great language, especially as it's one that you can get for free. If we build our technical knowledge, then we won't need third-party support which is a strong plus.

The PL/SQL performance is slow. If you have big batch jobs running in the middle of the night for a bank doing its end-of-day audits, then MariaDB will take three times longer than using Oracle. The product lacks sufficient detail in its reports. MariaDB has many extra features that would help to optimize the DB in the enterprise version and it would be helpful if it were possible to add some of those features in the open source version. 

I've been using this solution for two years. 

The solution is very stable in the right perameters. If I have a customer looking for something that's not batch job heavy, then we use MariaDB. If I have a core system that's going to take a ton of records and go through all these in the batch jobs at night, then we default to Oracle, because it's faster. We've proposed it to enterprise clients and we've proven to them that it's stable enough.

It's probably one of the most used RDBMS's for scalability. We haven't really tested it on millions and millions of customers but there's no problem with scalability. 

We use the community for support. If we were to purchase support, the cost would be around 5k per year. It's a big difference. We usually just use the after-market support and haven't required any direct support from the company. We've been able to handle it internally. 

When I compare MariaDB to Oracle, an industry leader, the big difference we found is performance in the PL/SQL mode. With Oracle, regular queries get executed at the same level with no issues. For ease of use and the setup, they're pretty similar. We also looked at IBM DB2 but there were compatibility issues and it was significantly slower. 

The initial setup is really easy for our team. It's a quick download and configuration. We have set parameters.

We use the open source edition which doesn't require licensing. We don't offer the enterprise edition, because if we're taking the customer off Oracle, for the additional benefits, we have to optimize the cost. If we have a customer with budget constraints, it's saving hundreds of thousands of dollars, sometimes millions, if we use MariaDB instead of Oracle.

I rate this solution nine out of 10. 

I would like to see a better user interface which would make the tool less complex.

I have been using the tool for three years. 

The product is stable. 

We have used MongoDB and MySQL before. 

The solution was easy to setup. 

We use the solution's free version. 

I am satisfied with the overall product. I would rate the product an eight out of ten. The product has good documentation and you can find many examples online. 

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.

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. 

My company provides solutions for banks, credit card companies, and other enterprises in the financial industry. 

MariaDB is a fast and flexible tool. 

Integration with AWS could be improved. 

I rate MariaDB nine out of 10 for stability. 

I rate MariaDB eight out of 10 for scalability. It's relatively good. 

We do not have paid support because we use the open-source version. If we have questions, we can look for answers online. MariaDB has an active user community.

I rate MariaDB seven out of 10 for ease of setup. Deployment is easy. We deploy it on-prem and on AWS. I am on a team of seven people, but one person is sufficient to set it up in two hours.

We use the community version of MariaDB. We don't have an enterprise license. 

I rate MariaDB eight out of 10. I recommend MariaDB depending on the use case. 

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.