MariaDB Reviews

It's a relational database, so it's mainly used for structured data. We use it for some of our in-house applications.

For us the benefit is that the system is very stable, so we don't have many outages. We also have a lot of experience with MariaDB, so we can optimally configure MariaDB and deploy a well-tuned environment.

I like the global transaction IDs (GTIDs) feature. It's quite reliable for replication between a master and a replica server, and it's a feature that MySQL also has but implemented differently. 

Another thing I like is the flashback feature, which allows you to roll back a transaction from the binary logs, so you can retrieve data. If someone deleted data, you can flash it back. That's a feature I really appreciate.

I'm interested in witnessing the integration of materialized views, which would enable the preservation of select queries. This particular functionality seems to be absent in MariaDB when compared to rival relational databases such as Oracle and SQL Server. The inclusion of this feature, akin to the offering from PostgreSQL, would be a valuable addition to MariaDB's capabilities.

I have nearly 13 years of experience working extensively with MySQL, and in recent years, I've also gained proficiency with MariaDB. Since MariaDB is closely related to MySQL, my combined experience with both platforms spans over a decade. Currently, we're utilizing version 10.4, although it's a few iterations behind the most recent release. We're actively preparing to undertake an upgrade in the near future.

It is a quite stable solution. 

If you want to scale it for larger use cases, like sharding, you'd need to consider MariaDB SkySQL or Xpand, which is a separate product designed for cloud deployments. So, for realistic scalability, especially in the cloud, you might need to use MariaDB SkySQL.

We have a couple of hundred users currently working with the database. It's probably around 400.

It's currently deployed on-premises, but we're planning to move it to the cloud in the future.

It's not difficult to maintain. It does require some maintenance, but it's very stable. You don't really need to intervene much, so it's quite stable. The main maintenance we do is patching and upgrading once a year. So it's not too taxing to maintain.

I have used MySQL or Oracle products. 

MariaDB, being open source, is a significant advantage, especially considering we use the enterprise edition. It's considerably much cheaper than Oracle, which is a proprietary database with high licensing costs. So, from a financial perspective, MariaDB is far more economical. 

Another advantage lies in its robust online community, simplifying troubleshooting and assistance. While we do have enterprise support, the online community and resources are quite valuable. 

As for cons, due to fewer contributors compared to other databases like MariaDB, certain features might experience slower development. Amazon and MariaDB Corporation are among the contributors, but it's an area that could use more attention. However, overall, MariaDB remains a strong choice.

MariaDB emerged as a distinct entity originating from MySQL, rather than being an inherent part of it. Formed in 2009 due to apprehensions that Oracle Corporation might negatively impact MySQL, which they acquired in 2010.

When deciding between MySQL and MariaDB, the feature disparity is minimal. MySQL has adeptly upheld compatibility since the transition, making it primarily a matter of personal preference. Some features differ between MariaDB and MySQL, catering to unique preferences.

In essence, MariaDB is a highly favored relational database, a commendable choice within the relational database realm. For those seeking a relational database, MariaDB stands as a solid option. As for purchasing a database, MariaDB comes highly recommended. It claims the second-highest rank globally and holds the second spot in the DB-Engines ranking. MongoDB ranks a bit lower, but the choice between the two is essentially equivalent.

On the whole, I would assign a rating of seven out of ten to this solution.

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.

I use MariaDB since my organization has different customers who use different databases. My company caters to the customers' needs depending on the database they want to use.

The most valuable feature of the solution is a relational database, which is fairly reliable. My company is satisfied with most of the features of the solution. My company just provides services to customers depending on what they want, so we don't necessarily dig too deeply into why they want it. If a customer asks for a referral or suggestions for a free database, then my company normally tries to push PostgreSQL, a tool we get directly from the vendor.

My company hasn't seen any problems with the solution where it has been running. The solution works fine for the purpose it is meant for, so there are no issues.

MariaDB should provide HA and archive logging. If HA and archive logging are present in the solution, it is hard to find them. The aforementioned details related to HA and archive logging need to be considered for improvement. I haven't had the opportunity to use the features provided by the solution since I don't know how to see them.

I have been using MariaDB for a couple of years. My company operates as a consultant offering support for the solution.

It is a stable solution. I haven't seen any stability issues for the purpose MariaDB is meant to function.

In my company, the instance related to MariaDB is fairly small, so I can't comment much on its scalability.

For MariaDB, my company has only one customer who uses it for a single instance, which is about 20 GB of data at the moment.

I haven't had the need to contact the solution's technical support.

The solution is deployed on an on-premises model.

MariaDB can be deployed in a day.

My company uses the free version of the solution.

With PostgreSQL, it's simply the archive logging functionality and remote hard clustering capabilities.

My company is not familiar with how the functionalities of PostgreSQL would work for MariaDB or MySQL.

I would tell those planning to use the solution that it is pretty much the same as MySQL, but since my company has dealt with only one instance in MariaDB, I can't say much about it.

I rate the overall solution an eight out of ten.

I installed the solution here in the company when they required MySQL. I tried MariaDB instead, and it works fine due to the fact that MariaDB is an exact clone of some parts of MySQL. It also has a database for a help desk solution, called a GPLI.

It's open source. It's freeware. It's very similar to MySQL. MySQL is a very good database management system, a relational database management system. However, the problem, or the potential problem with MySQL, is that it is under Oracle's umbrella, and I want to be prepared in case it's being commercialized and closed.

MariaDB was created by the same creator of MySQL. However, before he sold it to, at that time, Sun Microsystems, it was later acquired by Oracle. It's the same creators. It's the same programmer. That's what I like.

It's a one-time installation and configuration, and then I almost forgot about it. What I like is that it's very easy to configure, and just from time to time, you can make your backups, and that's it.

I don’t have any particular issue with the solution. It works well for my purposes.

I’m not sure if it can scale, so I’m not sure how it would fare for significant companies. I know that MariaDB has a cluster solution that I don't need at the moment. Probably, it would be a good idea to have a way just to confirm that the cluster is available for when I require scaling.

We’ve been using the solution for one year.

It’s quite stable. I haven’t had issues with bugs or glitches. It doesn’t crash or freeze. It’s reliable. It’s very similar to MySQL.

I’m not sure if it is scalable. Scalability doesn’t affect me as I am only using one application. I don’t require any scaling capabilities.

Indirectly through the help desk solution, the whole company has about 60 plus users on this product.

It's open source and freeware. The support that I receive is in the forums and the blocks in the internal information. You can’t call or email someone at MariaDB.

We also use SQL Server Express, MySQL Fork, and SQLite.

The setup is simple. It’s as easy as setting up MySQL.

This product is open-source and free to use.

I am just a customer and an end-user.

I'm not sure right now which version we are on.

Whether or not this is a good solution for a user depends on usage. You need to be sure that this is the solution for you. I'm not going to scale up, which is why it's my current solution. If I had to scale, I’m unsure if this would fit.

I’d rate the solution nine out of ten.

We use MariaDB for any instance where we need faster retrieval and processing rates, such as establishing relationships between data entities through entity relationship mapping. MariaDB is our preference for structured data, like user details or product information. However, for handling non-structured data, such as metadata, we prefer DynamoDB or MongoDB.

MariaDB is inherently faster than MySQL database. However, given the opportunity, our team would have likely chosen Postgres for better performance in terms of concurrency, etc.

MariaDB is likely less resource-intensive than Postgres and other RDMS solutions because it offers only a subset of features.

Concurrency is a challenge in MariaDB.

I have been using MariaDB for a year.

Ten engineers are using this solution.

It's open source, but there are no dedicated technical support resources.

The deployment should be easier because we use AWS EC2 instances to run and deploy the image and the services. It took a few hours to complete.

It's an open-source solution that only charges for a server database.

I rate the solution's pricing an eight or nine out of ten, where one is expensive, and ten is cheap.

A few EC2 instances are running that solve the MySQL and the service. 

Cross-functional GUIs are currently available. For example, we use DB Workbench, a solution that provides a GUI interface for MySQL, PostgreSQL, MariaDB, and several other databases.

It is seamless unless we want more advanced features, like simple database charting or event scheduling, which MariaDB doesn't support.

Our security team and platform team maintain security features. So, it depends on the type of protocols they use.

There are no particular challenges because the development kit, such as all the SD cases that are DB connectors, is well supported by Python and Java.

Our AI projects' data comes from non-relational sources like Mongo and Dynamo. Therefore, there's no direct correlation. However, MariaDB merely serves as a repository for information, such as profile data or some form of structured text (NTT), which can be displayed in tables or otherwise.

It depends on whether they prioritize performance and features. If so, they might prefer Postgres. However, MariaDB could be the better choice if they prioritize a time-tested solution and lower costs.

MariaDB offers more features than its competitors. It supports features like sharding and concurrent connections.

Overall, I rate the solution an eight out of ten.

I use MariaDB in my company for the deployment of web applications. MariaDB serves as a database software for web applications.

The most valuable features of the solution are that it is very stable and reliable. I like the fact that MariaDB is an open-source product and not resource-intensive. MariaDB runs on most of the operating systems of Linux. MariaDB is a cross-platform product, making it a great database choice.

MariaDB is a bit technical product, so whoever uses it will have to read a lot of documentation, which I don't think is a disadvantage of the product as it is just its nature. I believe that open-source products, in general, are a bit more advanced than regular systems. The difficult part related to the product stems not from the tool itself but is related to learning how to implement the product in the right way without creating any wrong configuration that could cause security issues or performance issues.

I have been using MariaDB for five years.

It is an absolutely stable solution.

It is a scalable solution.

Two or three people in my company use MariaDB.

I never had the need to contact the technical support team of MariaDB. I would usually find MariaDB's documentation and details online to read about how to deal with issues. Usually, issues in MariaDB are related to configurations more than stability as long as you make sure you install or use the stable version, which is considered to be a long-term supported system.

I moved from MySQL to MariaDB. MySQL is less maintained compared to MariaDB. Feature-wise and stability-wise, MariaDB is way better than MySQL from Oracle.

The deployment process of MariaDB is easy, provided you go through its documentation.

The solution can be deployed in ten to fifteen minutes.

Users can take care of the deployment part of the product by themselves, though, at times, it may depend on the project size that you plan to support with the software. If a project demands software that offers scalability and very high availability, the deployment process may take an entire day with many experienced engineers. If the deployment process is carried out for a single small system, it takes around fifteen to thirty minutes.

The solution is deployed on both the cloud and on-premises.

Quarterly maintenance is required for the solution. When some security incidents occur, the solution's maintenance may be required. If a security issue related to the system is revealed online, it would need immediate maintenance. Maintenance is required depending on the updates provided by the product, which usually occurs once a month or once a quarter.

One person in the company can take care of the maintenance phase of the product.

I rate the overall product a nine out of ten.

MariaDB provides a platform for developing our company's database.

The most valuable features of the solution stem from the fact that it is an open-source product and offers its users great online community support.

Sharding and the platform's vertical and horizontal extension and growth or scalability are areas with shortcomings that need improvement in MariaDB.

I have been using MariaDB for three years. I am a customer of the solution.

It is a very stable solution.

The solution is not scalable.

Around four people in my organization use the solution.

MariaDB is an open-source community software, meaning it is based on the generosity of others. I rate the technical support a six out of ten.

Neutral

The initial setup of MariaDB is easy.

The solution is deployed on an on-premises model.

Regarding the time taken to deploy MariaDB, I would say that in our company, we are still playing around with the platform. Our company is in the middle of a pivot right now, meaning we have plans to change our direction.

MariaDB is an open-source software, meaning I don't need to pay for the product.

I have no objections to the maintenance phase of MariaDB since I feel it is fine and easy.

I recommend the solution to those who plan to use it.

MariaDB is a community-supported product because of which I am not familiar with the paid support options that may be available.

I rate the overall solution an eight out of ten.

Our software development team uses MariaDB and other databases as the storage facility for some of our applications.

Initially, we liked this solution because it is a drop-in replacement for MySQL.

The most valuable feature is that it uses multiple cores, which is better than some of the other databases. When we have eight or sixteen cores, the utilization ratio is a bit higher than previous versions of MySQL. I think perhaps the enterprise version of MySQL may have better support, but the free version does not work as well as MariaDB. This is with the factory default settings.

Scalability is an area that needs to be improved.

When we have had issues with accidental computer shutdown or a power outage, our MariaDB database was corrupted. This did not happen with our Oracle or Microsoft SQL Server, so I think that there might be some differences in the database engine that better deals with these kinds of accidents.

We have been working with MariaDB for seven years, since 2013.

We have not experienced much in terms of instability. We have been running our instance since 2013 and it needs almost no maintenance. You just install it and forget it. It's that easy.

MariaDB works with just a little configuration for a small dataset, but it does not scale as well as Oracle of Microsoft SQL Server in our applications. For example, additional manual configuration or tweaks are needed so that a query will return in a reasonable time when there is a high volume of records.

Our client has between 10 and 30 concurrent users.

Getting proper support is sometimes difficult because when you have a technical issue and use Google to try and find a solution, there will be millions of results. You have to tackle it by yourself but even if there is the same error message, you can try every posted solution and it still might not work. There is not a single source of truth that you can rely on.

The initial setup is straightforward and I think that the installation can be completed in a couple of minutes.

We have our own team for deployment and maintenance.

I think that for a small team of fewer than ten people, such as a couple of developers, MariaDB is a very easy start. When the team size grows or when the complexity of the application grows, you might need to try other options such as Ingres or MySQL. In our case, at the very beginning, MariaDB covered almost every technical requirement for releasing version one of our application.

It is definitely a good start. Once the product has grown to a point where the developers know in which aspect MariaDB does not fulfill the requirements, then it's time to find a better match.

At this point, I cannot think of any additional features that I would like to see because most of what I want is already on the roadmap. I think that they plan to implement them one by one.

I would rate this solution an eight out of ten.