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.

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.

We are a solution provider and MariaDB is part of an offering that we deploy for our customers.

What I like best about MariaDB is that it is open-source and reliable.

Master-master replication is something that needs to be simplified.

I would like to see support for deploying MariaDB as an embedded database.

I have been using MariaDB for three years.

This is a reliable product.

Scalability is not an issue with MariaDB. We have deployed it to lots of our customers.

I have been using the Community Edition that does not come with support, but the documentation is great. Enterprise support is available for those who are using a licensed version.

Prior to MariaDB, I was using MySQL. After it was taken over by Oracle, we made the shift to MariaDB.

The initial setup is straightforward and it takes approximately half an hour to deploy.

I handle the deployment for this solution myself.

I used the open-source version, which is available free of charge.

This is a good product and I absolutely recommend it.

I would rate this solution a ten out of ten.

The tech stack we commonly use is Appian, which inherently integrates with MongoDB. This eliminates the need for selecting third-party databases or certifications, as it seamlessly works with MongoDB.

There is the need for a robust IDE for MongoDB. The existing PHP admin console doesn't meet the client's requirements effectively.    

I have been working with MariaDB for the past two years. 

It is stable. We have deployed several fraud implementations on Maria. While there have been occasional hiccups with replication and such, those can be addressed at the application level.

In terms of scalability, I don't perceive any issues with MongoDB, given the substantial volume of clients we serve.

I haven't encountered any blockers so far, which is why I haven't sought support.

Our technology partner, Appian, handles the provisioning, configurations, and instant spin-up of resources for us.

For clients predominantly using Microsoft technologies, especially Microsoft SQL, it aligns well with their technical stack. MS SQL is particularly suitable for reporting and analytics purposes.

It ultimately depends on the specific solution we are working on. However, overall, it is a good choice when considering factors like cost, performance, and other database practices. I don't foresee any significant challenges. I would rate it 7 out of 10.

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.

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.

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

We are a software and service provider and we have a lot of customers who are using our platform on the backend, which includes MariaDB. Our platform is for cloud telephony and the interface is the PHP Laravel Apache Platform. We have a hosted PBX platform and we are using Asterix as a telephony server. MariaDB is the database part of the solution.

MariaDB performs well as the backend database for our cloud-based telephony solution.

With respect to clustering and the master-slave configuration, sometimes the slave goes out of synch. If one server goes down then the other server in the cluster should be able to handle the load. If the synchronization were better and it was easier to maintain the cluster then that would be an improvement.

I have been using MariaDB for almost five years.

The stability is good, although in clustering, with the master-slave configuration, sometimes the slave goes out of synch. To that extent, stability becomes a challenge and is impacted because we want both the master and slave to be in-synch.

We have a lot of customers who are using our platform on the backend. Also, there are a lot of customers using our telephony product on the front end.

We have five or six clusters and as our business grows, we plan to use it more intensely.

We have our own technical team and to this point, we have not subscribed to receive technical support. However, we are thinking of taking it now because sometimes we have difficulties. There are a number of companies who do provide technical support.

The installation is straightforward, but depending on how efficient you want to make it, it can become complex. You have to have a good level of experience to be able to use it. Otherwise, there can be problems and you won't be able to handle it.

My technical teams, including the development and instructure teams, were responsible for the deployment.

This is an open-source product, which can be used free of charge.

We have not compared this product to many others. 

Our use of MariaDB is very basic, so it's a good platform compared to many others.

As it is a good product, I can recommend it to any users. If you want to have paid versions then there is Oracle and Microsoft SQL, but MariaDB is quite good and unless you have some specialized requirements, of which I don't know what they could be, you can use mariaDB.

I would rate this solution a seven out of ten.