MariaDB Reviews

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.

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 ability to deploy or store data that is accessed via the web is one of the solution's most valuable features.

The solution is also free to use.

The interface should be more user-friendly. It should be able to connect directly to the database and Interact with it without having to use commands. It needs better integration.

In future releases, it would be helpful if they could create an administration portal for the database to help manage it.

The solution is very stable. It was originally built under MySQL. It has a similar level of stability.

The solution is very scalable. We have about 230 employees using it on the intranet currently, and about 5,000 students on our eLearning system.

It's an open-source technology, so there is no technical support. If you have issues, you can look to the online community for help or guidance.

We previously used MySQL. We switched because MySQL is no longer open-source. It's now owned by Oracle.

The initial setup was easy.

We implemented the solution ourselves.

We use the on-premises version of the solution.

I would recommend the solution. I'd rate it eight out of ten.

It has given us better Join algorithms, Connect Engine, and ColumnStore. I can choose hash join algorithms in order to speed up joins on large tables. The connect engine is still a bit clunky, but it’s useful and fairly versatile. Column Store is a very valuable tool for analytics workload. I used InfiniDB in the past, but it was plagued with bugs. I am glad to see that MariaDB has finally turned it into a reliable solution.

As a drop-in replacement for MySQL, it fit in perfectly with our solutions developed for MySQL. It gave us some highly needed new features.

I would appreciate support for materialized views.

We have used this solution for about three years now, since I abandoned MySQL.

There were seldom any stability issues.

There were no scalability issues.

I never needed technical support. We have many skilled technicians in our company and we solve all issues internally.

I had been using MySQL since version 3.x. of MariaDB. This made sense because it was a drop-in replacement. Concerning ColumnStore, we have been using a Column-oriented database for many years, especially Vertica and InfiniDB. We are a HPE Partner, but InfiniDB/ColumnStore is a valid replacement when customers cannot, or do not want, to pay the heavy license cost.

The initial setup was straightforward.

Most of our customers will not consider MySQL/MariaDB if they need to pay for a license. Unfortunately, it is still an Oracle dominated market. Normally, the community version is well accepted because no license cost is involved.

We have worked, and still work based on customers’ requests, with most commercial and open source databases: Oracle DB, SQL Server, PostgreSQL, and ECC.

If you want a reliable, easy to maintain database solution, I think that MariaDB on RedHat/CentOS is an option that every DBA should consider.

• Reliability
• Enterprise integration
• Documentation
• Certification
• Support

It allows us to have an alternative solution to licensed DB's.

It requires enterprise integration improvements from the security, and audit perspective (AD integration etc.). Also, existing integration into BI tools is not present.

I've used it for three to four years.

They provide a high level of technical support.

We switched due to a common OS integration strategy.

We switched due to a common OS integration strategy.

We are using the solution under the Oracle license. Since MariaDB is offline, we use its applications instead of MySQL. 

The solution offers all the principal features that are offered by MySQL, including the process which is used, features, function and system. 

The solution can provide SQL interface for data. 

The license should be cheaper and closer to that offered by MySQL, Oracle and other products. 

The solution needs more metrics on daily count. SQL Stripment should be addressed. 

We have been using MariaDB for the past five or six months. 

The solution is scalable.

We have not contacted technical support. 

Installation is straightforward. 

It took maximum of a half to one hour to complete. It is not a big deal.

The installation can be handled on one's own. 

There are two or three technical people responsible for the deployment. 

MySQL is under a license for Oracle, which means that it is free and cheaper than other systems and databases. 

When it comes to MariaDB, it should have a more cost-effective license. 

We use the solution with our Internal application. It is not cloud based. Work bench is the interface for MYSQL. An additional interface is also available there from MariaDB. 

Integration does not present an issue. It works plain and simple, as if it's MySQL. When it comes to installation, we can control backup systems and there is much data found there, no problem at all. Given the software, the integration works fine and I use the solution in Windows and Linux Ubuntu. The Linux platform has nearly an identical work queue.  

I have found the solution to be easy to use from the get go, around five months back. It is simple and secure. No problems there. 

There are 100 people making use of the solution in our organization. 

I would recommend the solution to others. 

I rate MariaDB as a six out of ten. 

We use MariaDB for a database. 

MariaDB is stable and the initial setup is straightforward.

Replication could be better, and it's not so simple. It would be better if they had a replication server. It would make things a lot easier. You need to have that replication server, but not in the same server farm. Then there will be a bit of latency between both because you should have one in one city and another one in a different city. That kind of solution should be more baked into every single database today.

Mirroring the database in a live environment where any record written on the production server replicates instantly across the fiber on the other server wasn't easy. Many people don't even bother with that, and they just run one server.

I have been using MariaDB for about six years.

MariaDB is stable. If it fell over and weren't good for us, then we wouldn't be having this conversation.

Oracle bought MySQL, and at the time they forked it, a whole bunch of people were like, "no, this is not nice." We read that saw what's in there ourselves, and that was our reason for switching to MariaDB from MySQL. It wasn't about who had better features because there's not much difference when you compare those two. But it's just a nicer energy and a nicer product. 

The initial setup was a piece of cake.

MariaDB is open-source and self-hosted.

I would tell potential users that If they want an open-source database that can handle huge volumes and is reliable and strong, then I would recommend it.

On a scale from one to ten, I would give MariaDB a ten.