MariaDB Reviews

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. 

We are using the MariaDB and we are using it to record the database for our EERP system.

MariaDB is valuable if the data growth is a little bit slow. That's why we use MariaDB. Otherwise, we go with other regular databases.

The initial setup is simple. 

The product has been stable and reliable. 

There's an enterprise version. However, right now, we are using free versions. Our chunks of data are a low amount of data. We'd like it to be able to handle more or to have something between free and enterprise that can handle more.

The maintenance and performance could be a bit better.

There is no available pivot table. There is no facility available in MariaDB.

The failed login attempt feature is not available.

I've been using the solution for one year. 

It's stable. There are no bugs or glitches. it doesn't crash or freeze. It's reliable. Right now, for example, version 10.4 is very stable.

This is scalable while you are using the Galera cluster and we can easily implement this.

I haven't really dealt with technical support. 

I had just one question about a failed attempt at login. One time I hit the database diagnosis. When I was trying to connect the database multiple times and got failed attempts. That's the only time I reached out.

The solution is pretty easy. It is easier compared to the Oracle database.

While there is an enterprise version, we are using the free version of the solution. 

I'm an integrator, not an end-user.

We're using the latest version - possibly 10.10 or 10.4.

I'd advise users to opt for the enterprise version which offers a bit more. 

I'd rate the solution seven 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 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 network services provider and we have the solution to store and process telecommunications infrastructure, network and customer services monitoring data. Our Monitoring applications rely on MariaDB to store, process and present telemetry data from different components of the network.

Previously, we didn't have a fast network monitoring solution that could be used to monitor everything we have on the network infrastructure. The solution has improved operations because all our customers are happy that we can provide them with high grade service monitoring . They're able to monitor services uptime, utilization and other statistics. The database stores a lot of additional data related to monitoring including inventory and notifications handling data.

The software provides a lot of information on what is happening inside the database. For most performance parameters  it is easy to know if something is not right in the configuration or optimization which helps engineers take remedial finetuning measures. For example if the database is underperforming it is easy to know which performance parameter  can be adjusted to handle the workload. It is difficult to troubleshoot database issues if many performance parameters can not be monitored or debugged which is the case with some  database management systems.

It provides great monitoring data storage, processing and performance stability which is really important for real-time data storage and processing. It's a user friendly product.

I'd like to see more time series data and additional partitioning support, natively if possible. I started using  MariaDB but then migrated one of my systems to PostgreSQL because it has good support for time series data, plus there's a plug-in that PostgreSQL uses for easy support of time-series data and partitioning and it is easy to use. MariaDB could have something like that which would provide better support for times series data and partitioning. Automatic partitioning would be helpful is natively supported, because at some point I experienced issues with database performance. Partitioning is a bit complex and we do everything in-house.

I'd like to see something that does automatic optimization or tuning. This will particularly be helpful to new users.

I have been using MariaDB for 4 years 

Performance and stability are good with small instances and average skilled database administrators to maintain it, we haven't had any issues with small instances. For large instances that handle a lot of ingress data and queries, good stability can be attained with high level tuning which requires highly skilled database administrators who can correctly tune and partition databases if needed.

We haven't really scaled it and we're still using the open source version which can also  be easily scaled if needs arise.

Our company runs on a tight budget so we haven't got any support, we do everything ourselves. I know from others who have implemented and have commercial agreements with MariaDB that the support is good but I don't have first-hand experience.

I used a monitoring system that used flat files to store monitoring data and at some points used MySQL for some systems

The initial setup was very straightforward, not complex at all. There are so many resources from the community.

We implemented in-house

I can confidently say 90%

There are no costs associated with this solution. It is a free and open source software although one can opt for a paid support from MariaDB

Yes I did evaluate other options. SQLite, Oracle DB, PostgreSQL and MySQL

I would recommend that if a company wants to do everything in-house and doesn't have technical support from MariaDB, it is important to have good database administrators, because the initial setup is straightforward, but a lot of optimization is needed, and it requires skillful database administrators. I recommend some good planning from the beginning, and it is important to figure out whether the company needs to do some database partitioning. Carrying out good research from the beginning is the wisest course when choosing MariaDB as a database. That will be so helpful in avoiding possible performance and tuning issues.

I rate this solution an eight out of 10. 

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. 

The most valuable feature of MariaDB is the replication mode.

MariaDB has to improve from a management perspective. There is not much available for querying internal views to provide information for the operations team. Most other databases such as Microsoft SQL Server, Oracle, or even PostgreSQL, have a big set of internal views that you can query to understand what is going on, if anything is wrong, or how to improve.

I have been using MariaDB for perhaps two years.

This is a very stable solution.

MariaDB is very scalable.

I have had the opportunity to speak with technical support and I am satisfied with the outcome.

The process of setting up MariaDB is very fast.

The price of this solution represents a very good compromise between the cost and what it offers.

There are many valuable features in MariaDB.

MariaDB is a very good database when everything works fine, and I would recommend it. However, I work in operations and if something goes wrong there is no way to start an analysis because MariaDB doesn't provide many tools that help to understand the problem. In order to make this an enterprise tool, or an enterprise-level database, it needs to improve from this perspective. Otherwise, it will only be good for very small deployments.

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.