MariaDB Reviews

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. 

When I worked for Groupon in Korea, the main production database was MariaDB. We used it for eCommerce. It was a database where we stored data.

I would like to see more compatibility going forward. This would help if there is a need to change databases. E.g., if I change from MySQL 5.7 to another database, then MySQL could be the master database and this could database could be the slave. The replication capability is very important.

Two years.

I have not contacted the technical support. We haven't needed it.

We have recently upgraded to change our database and our production database is now MySQL 5.7. If someone wants to use memory based data, then MySQL is better than MariaDB.

We are using MySQL but MariaDB can solve things better than MySQL. Maria DB has better performance than MySQL.

Sometimes Percona is better.

MariaBD is good. It is almost perfect. I would recommend it.

I would rate this product as a nine (out of 10).

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.

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.

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 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.