MariaDB Reviews

There are no problems with MariaDB and it works fine.

The price could be less expensive.

I have been using MariaDB for more than five years now.

I have no problems with the stability.

MariaDB is scalable.

I have not currently had to use technical support.

The setup is not complex but straightforward. The time frame to deploy was about two hours.

I would rate MariaDB a ten on a scale of one to 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.

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 primarily use the solution for SaaS applications, where it is an integral part of our data management system.

The solution's features have effectively met our operational requirements as a standard SQL database.

There could be a command-line prompt for repairing the database and fixing indexes, similar to what was available in the old MyISAM storage engine.

I have been working with MariaDB for ten years.

I haven’t had any performance issues with MariaDB. Any problems we’ve encountered are typically related to the operating system or external factors like internet disruptions, not the database itself.

We have a small team of about three or four developers working with MariaDB. As for end users, the number varies depending on the application. Some of our SaaS applications support a few hundred users, while others might have thousands of users, depending on the client and project.

We transitioned to MariaDB after Oracle acquired MySQL. We continued using it just as we did with MySQL before the acquisition.

One issue I have experienced is with the InnoDB storage system. When a database crashes in InnoDB, it's essential to have a backup in a text file for restoration, but this is a common issue with MariaDB.

MariaDB differs from MySQL in several ways. Over the years, MariaDB has introduced many unique features that are not present in MySQL. It’s more open and community-driven, which allows for quicker adoption of new features and patches. Performance, especially in terms of scalability and handling large volumes of data, is a key difference. Additionally, MariaDB has better compatibility with some of the tools we use, making it a more attractive choice for our organization.

The setup was generally fine, but the configuration can be scattered across directories, which slightly complicates things. A more streamlined configuration process would be beneficial.

I set up the product's functionality replication on a virtual private network with a separate database server, which has significantly improved our data management. Although we have not yet scaled to the point of needing multiple clusters, the replication setup serves as a real-time backup for disaster recovery purposes. The product has been highly reliable, and regular updates as part of our server maintenance routine ensure smooth operation.

My overall experience with the product has been very positive. It has consistently delivered excellent performance and stability across our various projects. We have encountered very few issues over the years, and when we have, the community support has been strong, assisting us in resolving problems quickly. Its reliability is crucial for the critical applications we run.

The learning curve is quite manageable, especially for those already familiar with MySQL. The two products share many similarities, so transitioning from MySQL to this solution was relatively seamless for our team. Comprehensive documentation and active community support further simplify the learning process, making it easier for developers to get up to speed.

We have used it for a long time, proven very stable. Additionally, it is an excellent alternative to MySQL, especially considering the changes after Oracle's acquisition. The strong community support and integration with our existing infrastructure enhance its value.

I rate it a ten out of ten.

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.

I am currently using Visual Studio Code. I have used Visual Studio for about six months, along with GitHub. Additionally, I use GitLab for Azure orchestration.

The unit testing and Git are integrated. The searching is very extensive, which is helpful.

Visual Studio offers unit testing integration and extensive searching capabilities.

The Git extensions can be improved. The features available are very basic. Visual Studio should offer more extensive functionality in comparison to Git-focused software like GitTower or SmartGit.

I have been using Visual Studio Code for about six months.

I have not faced any issues in terms of stability.

We used to use Zoom for communication but have moved to Teams. GitLab provides what GitHub provides, so we don't use GitHub.

If you understand your project, you can install it without needing anyone else.

The IT department handles certain aspects, and I don't have information about it.

We are using Microsoft Teams instead of Zoom. I also mentioned GitLab, Redmine, Mongo, and GitHub Copilot is something we've considered but haven't started using.

I'm not the right person to ask specific questions as I do not have access to certain details.

I was just creating databases and doing research, basically. I've been creating new services and updating those databases in MariaDB. So, I've been learning all the SQL stuff, exploring it on my ID. This was for personal use, not for a company.

It's user-friendly. It's easy to use.

The configuration could be improved. It should be easier.

I have been using MariaDB for just three or four months, I got started exploring it. So I can work with it, not an expert, but I've been using it for three to four months now.

For non-production purposes. I'm just using it for my personal project, so it works quite well. I haven't faced any errors yet.

I haven't reached the production phase. So, if I were doing any projects, I was the only user.

The initial setup is not complex at all. Once you get used to it, then you can figure it out. Starting becomes a bit difficult, but once you get into the flow of all the programming, make all the language and stuff, you get to know it. It's quite easy.

For my setup, I used my command line. I installed an ID for that, so I interact with MariaDB through that.  

I used the free version. I didn't purchase it. 

I would suggest do your research first, especially regarding security. You should probably search for reference materials for MariaDB, and then you should get into it. Don't just dive straight into it. You should have done some sort of research before getting into it. That would be my advice.

Overall, I would rate the solution a seven out of ten.