MariaDB on CentOS Reviews

I always use MariaDB on CentOS for performance testing, as my main job is to analyze all the issues after the load test. Performance testing is the central use case.

With 10 years of experience with the product, I think the biggest advantage is that it is easier to maintain than Oracle. Both Postgres and MariaDB are definitely embedded with Docker, and it is really easier to change, modify, and maintain than Oracle.

For the moment, I did not see any advantage of using Galera Cluster. I prefer to work on Docker because it is easier and faster for me.

MariaDB on CentOS may have some negative sides against Postgres. To improve some requests and modify low-consume requests is a bit longer than with Postgres. Postgres is easier to work with because you can use the explain plan to see directly and immediately if your new request is good or not. This is the main point. MariaDB is a bit complicated and a little bit tough.

I have been working in APM for up to 25 years.

MariaDB on CentOS is stable, more or less. I would rate the stability at seven points.

The scalability of MariaDB on CentOS depends on the use case. In my opinion, in my use case, the scalability is good. I would give a rating of seven for scalability.

The technical support or community support for MariaDB on CentOS is bad. There is a main problem with all the companies that sell this kind of tool and services. The first level of support is the first one you reach. When you begin to have a more difficult problem, there is no one available because sometimes you need to update the call and recall on it. This is not good because when we have some big problem on the database, we need to have a database administrator, not a person who reads instructions on the screen. It is always the same problem. My rating is two.

The installation of MariaDB on CentOS is not complicated to do.

I cannot answer about ROI with MariaDB on CentOS. I have no idea about that. I do not see any savings from MariaDB on CentOS.

I am working with some testing tools today, and it is always the same tools. The big ones are LoadRunner and NeoLoad, and for APM I use Dynatrace. I also work with Grafana, but LoadRunner is my primary testing tool.

JMeter is an open source tool, and LoadRunner is from OpenText. I have not been using LoadRunner in the cloud. I work with Micro Focus solutions apart from LoadRunner. I use functional testing solutions such as HP ALM.

In terms of APM and performance monitoring, I work with LogicMonitor. I may also work with tools like New Relic and Dynatrace for performance monitoring, and Apache SkyWalking for performance. I work with backup solutions, storage, and database tools.

I have experience with CentOS, Debian, Ubuntu, and similar products. I have been working with MariaDB on CentOS for 10 years. I use Galera Cluster as a feature of MariaDB on CentOS. I cannot answer about the largest volume because I have never used MariaDB on CentOS with the largest volume. My experience with the largest volumes is only with Postgres and Oracle.

Postgres is easier for me because of the modification of requests. I do not know the difference about the license, as licensing is not my area. I use and maintain MariaDB because I am not really aware of the price of MariaDB license or Postgres licensing.

If asked to rate MariaDB on CentOS from zero to ten, with ten being the best, I would give it a rating of seven. The compatibility with MariaDB on CentOS and SQL is good. I do not have experience with MySQL currently because the most database that I work with now is Postgres. I do not know about the advanced security features of MariaDB on CentOS because I do not work on security and am not skilled to answer that.

I use AWS as my cloud provider. I do not have experience with AWS Marketplace as it is not my area.

My overall experience with MariaDB on CentOS is seven. My review rating for MariaDB on CentOS is seven.

I use MariaDB on CentOS as a database for other applications, and in our field, we need absolute availability. MariaDB on CentOS offers, with an additional product called Galera, a very dependable solution, and I am very enthusiastic about it.

At the moment, I am setting up a cluster of MariaDB on CentOS.

The Galera Cluster feature has helped me with high availability because it is stable, requiring at least three servers to have a stable cluster. If one member of the cluster stops for any reason, the service continues working, and as you restart the server, it synchronizes everything with the other members. It is very well designed; while it is a complex feature and is documented, every improvement in this area would be helpful, and this is a suggestion for the Galera and MariaDB on CentOS developers.

MariaDB on CentOS is a very good SQL database that is open source, meaning no license cost for users. There are even commercial editions that offer support, but basically, you do not need to pay any license. It is very dependable and very clear.

You can always improve a product, and the area that is very sensitive in MariaDB on CentOS is the release and the backward compatibility.

I have worked with MariaDB on CentOS for five years; however, MariaDB on CentOS is not my central focus.

I rate the reliability and stability level of MariaDB on CentOS as very high; it is among the best databases that I have ever seen. Compared to another database, PostgreSQL, for example, I find PostgreSQL is not a bad database, but as far as clustering is concerned, it is a bit confusing, and the documentation is not as good. I prefer to work with MariaDB on CentOS and even for Microsoft SQL, their documentation and experience with clustering is not as good as here. Among these three databases, I would give a 10 to MariaDB on CentOS, a 9 for PostgreSQL, and a 9 for MS SQL.

I rate how scalable MariaDB on CentOS is as lacking experience in this area; I know there is an issue, but I have never performed real tests. For example, several years ago, a customer wanted scalability tested on another technology, LDAP, with two million objects, and that was acceptable. If somebody comes to me requesting to test with 60 million objects, I will do that test, but it is demanding and I am not going to do this just for the sake of it.

I have never gotten in touch with technical support for MariaDB on CentOS because I was able to solve the problem autonomously. I did not need that, but they send me from time to time mailings or making offers, which is perfectly appropriate.

Positive

Before using MariaDB on CentOS, I used both MS SQL and PostgreSQL; if the customer absolutely wants MS SQL, we make the installation with MS SQL, but if the customer asks me what the preferred solution is, I am going to suggest MariaDB on CentOS.

My experience with the initial setup of MariaDB on CentOS is that it is complex, but the documentation is better than PostgreSQL. It is highly standard SQL, so it is not really a difference; I am more of an infrastructure person than a database person. I am interested in stability, not the language, and I find the good standard SQL from my point of view is acceptable.

I am working with many technologies, including a quite old and stable technology named LDAP, Lightweight Directory Access Protocol, and some relatively new technologies for us, such as a Linux database called MariaDB on CentOS. Every day I encounter new technologies.

I have not tested MariaDB on CentOS with a very high volume, but I test technologies and if I find a good technology, I offer that to the customer, and the customer can ask me to test this with X millions of objects. Basically, I stick with the feature that I need most, which is reliability and cluster capability.

Overall, for MariaDB on CentOS, I am certain I can vote 10. CentOS is very good, even a 10, but I must inform you that CentOS is moving away and transitioning to followers of CentOS called Rocky Linux or other names. At the moment, I was forced to migrate from CentOS to Rocky Linux. A very interesting question for everybody would be a comparison between the open source Linux distributions, such as Fedora, SUSE, Rocky Linux, and Ubuntu, which is in high demand. I would rate my overall experience with MariaDB on CentOS as a 10.

MariaDB on CentOS was used for basic managed WordPress hosting, having all the databases of customers with WordPress websites. Regarding my use case with MariaDB on CentOS, we also took MySQL dumps, which is similar in MariaDB. We also used replication sometimes for those MariaDB instances. Sometimes, we needed to use some queries to check the max connection on the database; these are a few things that we were doing.

The best features of MariaDB on CentOS, in my experience, are that it is mainly enterprise-friendly. We can also manage MariaDB on CentOS through systemd and systemctl, which runs on CentOS. It also has SELinux support, and the package management is easy and reliable through those package managers, YUM and DNF. MariaDB on CentOS is reliable and very good for production.

The reliability and ease of management of MariaDB on CentOS helped me day-to-day, for example, because the company I worked for used to host all the customers' databases under the cluster. It was not a single database for them; the customers could access their individual databases, but for us, it was very good to go into the big box and then enter the MariaDB on CentOS engine, where we could run queries on multiple databases. That made it easy to avoid going into single databases to do it, so multiple queries to update multiple databases for a single table were things that made it easy.

MariaDB on CentOS impacted my organization positively, helping in database redundancy. It helped to have MySQL dumps, so if a customer removes their database entries, we could easily pull the dumps to provide the backups to the customer. That's how it was done, and it made things easy.

Regarding MariaDB on CentOS and reduced manual effort, there were scripts automating the backups. The MySQL dump feature in MariaDB on CentOS helps to take the dumps. Also, since it runs on systemd, when a big server reboots, the engine starts up, causing less downtime.

MariaDB on CentOS has older versions than the latest upstream releases, so package versions can be older, and that's something that should be improved. CentOS is also at end of life, so I'm not sure; I have not run it on the latest RHEL versions like AlmaLinux. Perhaps they have improved now. Also, since it is a fork of MySQL, repo management is a little tricky.

Regarding needed improvements for MariaDB on CentOS, the database version testing took time, so perhaps the provider could work on that.

I used MariaDB on CentOS for around two to three years when I was working for a web hosting company, where they used MariaDB on CentOS.

MariaDB on CentOS is pretty stable; I have not seen the engine going down.

Regarding the scalability of MariaDB on CentOS, if you're referring to allotting resources like increasing the max number of connections and things such as that, it's pretty scalable. The configuration file is available, and we can make the changes and restart the MariaDB on CentOS engine; it is pretty approachable once it is done.

I have not needed to reach out for help regarding customer support for MariaDB on CentOS; I think it was done by the admins.

The organization was using MariaDB on CentOS only. I used some other products, such as PostgreSQL, which I think is better for backup products, but for WordPress and things, MariaDB on CentOS is better.

I have seen a return on investment with MariaDB on CentOS; the management is easy. The support engineers could run queries without needing DBA admin level knowledge to perform some functions, so you do not need to hire MySQL admins every time. It was good, and it also saves time with the easy deployment; everything is good.

This was an organizational decision, and it wasn't on me; I did not evaluate other options before choosing MariaDB on CentOS.

I would rate MariaDB on CentOS a seven out of ten.

I chose seven out of ten because it needs some improvements related to optimization and the upstream packages. However, seven is a very good number because it also has the feasibility of MySQL dumps, and it's a fork of MySQL. The configuration is very easy; you can configure the ports and things such as that, and it's compatible with SELinux, so that's why.

Regarding MariaDB on CentOS's AI capabilities, I'm not sure how it works with AI, but the governance and security capabilities of MariaDB on CentOS are good. We can set the root password for it, and the governance is also easy; we can automate it or have different users. The different user roles, levels, and permissions make it a good product to govern.

The output of MariaDB on CentOS is very reliable; the queries are similar to MySQL. Because it's also a fork of MySQL, the queries are reliable, providing very accurate results. You can use all the operations of MySQL and it gives very accurate results.

For others looking into using MariaDB on CentOS, I would say they should be very familiar with SQL queries, as you can run any complex queries on it. However, they should also not expose some open ports and ensure that the configuration is good to avoid outrunning the RAM.

MariaDB on CentOS was introduced to me about three years ago when we were finding a proper solution for a relational database that can be reliable and open source.

We primarily use MariaDB on CentOS for transaction storage, specifically for payments that are being created. We are using it in our projects involving iGaming and finance. We are primarily using it for reliability.

When we were looking for a reliable database, what we found is that on CentOS, MariaDB is the default and it is faster in some cases than regular relational databases with respect to some queries. For our business logic, we need to have querying capabilities that provide cumulative reports based on the transactions we are having. We have so many transactions, approximately one million transactions in a day. Because every operator that has been using it is using the same database, we need to create cumulative reports for their respective operators to provide them a daily analysis of what has been transacted, gross revenue, net revenue, and other metrics. From there, we started using MariaDB on CentOS.

We consider MariaDB on CentOS as the first way to implement solutions. For every business, we consider MariaDB as our primary database. Although we have MongoDB and other things, those are just for collecting data. For reliable data solutions, we only consider MariaDB on CentOS.

MariaDB on CentOS is deployed in our organization not on-premises. It is on AWS, and we also have an instance in GCP. We use AWS most for MariaDB on CentOS.

Our client purchased MariaDB on CentOS through the AWS Marketplace. I do not have access to that information.

On RDS and AWS, we were having so many instances that handled the connection pool. What happens sometimes is that the pool gets exceeded and the RDS cluster cannot handle it. It spins up a new reader instance. We have a master-slave architecture, so with respect to that, it creates and spins a new reader instance, which takes time, and then after that, it allows that connection to be working. However, in between that, we lose speed because we do not hold that many connections if our load increases. This happens only at night. When we are sleeping, the connection goes up and with respect to that, the system gets down for a while just because of connections. For this issue, we need to pay. The alternate and the best solution we found was MariaDB on CentOS, which handles all this with ease. After implementing this, we did not find any issues of this type.

MariaDB on CentOS is very much scalable. We can have multiple reader instances, and we follow a master-slave architecture for a relational database. There is only one master, and there is too much load being handled seamlessly, and with respect to that, it is working as expected.

MariaDB on CentOS has positively impacted our organization in several ways. We were on a different relational database and that was not holding that much connection and that much speed. After implementing MariaDB on CentOS, it gives us so much ease to handle those issues. From getting 18 to 20 errors related to connection pooling, after implementing MariaDB on CentOS, we now have zero instances of these errors.

The best features MariaDB on CentOS offers is that it is a default database, so we can easily install it. It was a seamless installation out of the box. The other thing which we need and which MariaDB provides is the speed. For pooling and handling multiple connections on a single instance, MySQL and some other services provide their enterprise edition that we need to pay for. However, for MariaDB on CentOS, it is freely available and built-in. With respect to that, it is all seamless. We do not need to pay for anything, and we are utilizing the best connection pooling capability. We also got some performance speeds over our queries. It is also very much compatible. It is all the same as MySQL. It fully supports MySQL. It is already compatible with our previous projects, and if we introduce some new kind of thing, it can handle everything.

MariaDB on CentOS has positively impacted our organization because we were on a different relational database and that was not holding that much connection and that much speed. After implementing MariaDB, it gives us so much ease to handle those issues. It has things inside it so we do not even need to change the configuration; it handles it with very ease. The replication thing is very good, and we have fewer read replicas because of the connection handling. The reader latency is very less. We do not get any idea that the data we are fetching from a master to a slave instance is different because the reader latency is very less.

The primary thing that we got from MariaDB on CentOS is the connection handling capability. The connection was dropping, so that is totally resolved. We did not even find any single instance of this type of case after implementing MariaDB. The second thing is the speed. Sometimes it performs faster. When we do EXPLAIN and everything, it shows us what indexing it has been using, and they are much more efficient than the other relational database. It handles everything in a good way. It is a balanced configuration. By default, it provides a balanced configuration, so we do not need to look into that side. The faster query speed and the better replication feature that is open source, and we also have community support for that. The security updates are very fast. It also supports storage engines for different types of data we can simply use. One of the things that is not ideal is that the version which is default is sometimes older than the very latest.

MariaDB on CentOS can be improved just by providing the latest versions.

I do not think there are needed improvements for MariaDB on CentOS overall as the package is complete. Some kind of initial metrics that could be provided rather than having to be manually implemented would be helpful. If there is any kind of support, there already is, but we need something more stable.

We have been using MariaDB on CentOS for four and a half years.

MariaDB on CentOS is very much stable in my experience. If we compare to previous solutions, we do not even need to look into metrics extensively. We just look at them every week. Previously, we were looking at those on a daily basis, and we needed to figure out if these spin things would work good or not. However, here we do not even need to look at that part.

The customer support experience was great with MariaDB on CentOS. I did not even need to connect to customer support. The communities and the blogs are already available, and we referred to those to accomplish what we needed. We did not even need to use customer support, so that is a positive aspect.

Positive

We were on RDS clusters, and they were very good initially, but they have their drawbacks. With respect to that, we switched to MariaDB on CentOS.

We were thinking to switch from relational databases to document-based databases before choosing MariaDB on CentOS.

We were considering MongoDB as another option. These are just document databases, and they can scale with clusters and everything, but for reliability, we need a relational database. That is why we chose MariaDB on CentOS.

MariaDB on CentOS is very much stable. If you need benefits related to fast queries and connection handling as well as scalability, you should switch to MariaDB on CentOS if you are having so many connections and you need faster queries.

I cannot say it is as general as other relational database services, but we need to just find it. It should be defaultly available because it is providing so many features that we required. It should be highlighted more prominently. Regarding metrics, for the pooling connections and everything, we did not face any issues.

One more drawback that I can mention about MariaDB on CentOS is that some very specific tools, if we need to connect any client with something like MySQL Workbench or DBeaver, it shows some kind of warning about a version mismatch. They do work, but sometimes it shows a warning which we encountered. That does not make any logical sense, but it definitely shows a warning.

I have shared everything about MariaDB on CentOS, and overall, it is a good solution. We are happy to use it. I would rate this solution an eight out of ten.

My main use case for MariaDB on CentOS is as a database for my application.

A quick specific example of how I'm using MariaDB on CentOS for my application includes Laravel-based applications and WordPress-based applications as a replacement for MySQL.

The best features that MariaDB on CentOS offers are a reliable, high-performance database and an open-source solution.

Being open source reduces licensing costs and allows me to install it anywhere I want on any type of environment, and high performance is absolutely critical and mandatory for any application.

MariaDB on CentOS has positively impacted my organization by enabling us to use more recent versions of frameworks and improve the performance of the application in general. Using newer frameworks and improved performance benefits my team and business by providing a newer framework that is more secured, has better performance optimization, and allows us to integrate more new features.

I have no suggestions on how MariaDB on CentOS can be improved. There are no specific areas or features where I would like to see improvements in MariaDB on CentOS.

I have been using MariaDB on CentOS for about five years.

MariaDB on CentOS is absolutely stable.

As with any database, there are some challenges for scalability, but from the software point of view, I have no issues with replication or adding resources.

I have never used customer support.

I previously used MySQL and switched because the newest frameworks required MariaDB.

I have seen a return on investment through specific improvements in performance optimization for the application, resulting in a better user experience.

My experience with pricing, setup cost, and licensing has been positive since it is open source, and we did not have any issues with licensing and pricing. My costs are based on resource allocation for this database, which depends on the project.

I did not evaluate other options before choosing MariaDB on CentOS.

I would rate MariaDB on CentOS a nine on a scale of one to ten.

I choose a nine because there is always room for improvement for any software, but in general, it is a reliable, stable, and easy-to-use solution.

Regarding MariaDB on CentOS's security and governance, I think they are pretty secure if you configure it properly.

I have never used MariaDB on CentOS with artificial intelligence.

My advice to others looking into using MariaDB on CentOS is to not rely on default configuration and to secure it from the first minute of your work with MariaDB on CentOS. My overall review rating for MariaDB on CentOS is nine.

My main use case for MariaDB on CentOS is that we use MariaDB MaxScale for proxies. A quick specific example of how I use MariaDB on CentOS in my day-to-day work is that we install it using MaxScale.

MariaDB on CentOS works very well and provides high performance. The best features MariaDB on CentOS offers are global transaction IDs and GTID-based replication. Additionally, MariaDB now owns Galera Clustering, which we are not currently using.

GTID-based replication has helped me significantly because it makes the replication very robust. If a node goes down, it can resume, especially with MariaDB MaxScale, allowing you to resume replication very easily.

MariaDB on CentOS has positively impacted my organization with some good features in terms of administration. One such feature is flashback, which not many people are aware of, allowing you to roll back DML transactions without having to restore from backup.

From these features, I have seen specific outcomes such as time savings and fewer errors. Because we use MariaDB MaxScale with MariaDB async replication, we have noticed very little intervention in terms of failovers and high availability support, which is very useful.

To improve MariaDB on CentOS, I believe it needs materialized views, as stored procedures in MariaDB are not as good as those in Postgres or Oracle.

I have been using MariaDB on CentOS for about ten years.

MariaDB on CentOS is very stable in my experience.

The scalability of MariaDB on CentOS is good.

Customer support for MariaDB on CentOS is excellent and very good.

I previously used MySQL Enterprise Edition before MariaDB on CentOS. We switched because of the lack of support.

My experience with pricing, setup cost, and licensing for MariaDB on CentOS has been that we use MariaDB Enterprise Edition, so the cost and pricing are very competitive.

Before choosing MariaDB on CentOS, we needed a MySQL-like solution, and although we did consider Percona, we chose MariaDB.

My advice to others looking into using MariaDB on CentOS is to not treat it as a drop-in replacement for MySQL, as it is a completely separate database now with more features. You should look into the features and replication topology, which is quite different, and understand the storage engines and spider engine. You should definitely make sure you use Maria Backup for backups because it is a fork of Percona XtraBackup and understand the difference. The community is very good, and we need to see what direction they take on AI, as AI vector features look decent and very good so far. MariaDB on CentOS is very good, and they are looking at Kubernetes Operator now that supports async replication, which is something we want to look at in the future. I would rate this product eight out of ten.

The major use case for MariaDB on CentOS is that we are working in IoT; we have installed some NFC meters on the network towers, basically mobile towers, for collecting metrics such as voltage, current, load, and everything that consumes electricity, which we are storing in MariaDB on CentOS. It is a small project, so we directly went with it.

MariaDB on CentOS is effective in handling large data volumes; I have installed approximately 10,000 devices and it is working well. I have put MariaDB on CentOS behind a few systems and it is working for my 10,000 devices easily with no issues.

The biggest advantages of MariaDB on CentOS, from my perspective, are that it looks similar to MySQL, making it slightly lightweight and easy to install. We need to set up many things for MySQL, but I find MariaDB on CentOS lightweight, which is a main feature.

MariaDB on CentOS is easy to use and easy to install. The setup is straightforward and everything is the same as MySQL, so nothing is different.

I have seen a return on investment with MariaDB on CentOS in terms of time savings because time is money; saving time is also saving money. I have saved a lot of time due to its easy installation and use case.

For potential improvements that could be made in the future for MariaDB on CentOS, I think two or three things are needed; one is AI to support rewriting queries because at this stage every database supports AI. Another thing I have not seen in any database is an AI engine that analyzes a query and suggests a better way to write it. If I write any query, an AI engine could suggest that the same result can be obtained with a better query. This is something that could help me write better queries.

I have been working with MariaDB on CentOS for approximately one year.

Regarding stability, I have been working on my project for the last year and, while the project has run for four to five years, I have not seen any technical glitches from MariaDB on CentOS that caused downtime; it is working fine.

I have not run MariaDB on CentOS in cluster mode, so I cannot comment on its scalability.

I have used the community support and I can easily find answers to almost all my queries from there. The community is pretty good, so I got all the solutions I needed.

MariaDB on CentOS is easy to use and easy to install. The setup is straightforward and everything is the same as MySQL, so nothing is different.

I have saved approximately 10 to 20 percent of time and money due to MariaDB on CentOS.

I have not integrated MariaDB on CentOS with MySQL; I am running purely MariaDB on CentOS.

Regarding the security aspect of MariaDB on CentOS, I have used SSL, and I also use RBAC, role-based access control. I mainly use these two. I am satisfied with the security aspect.

Regarding any negatives in MariaDB on CentOS, there may be some minor improvements, but I have not seen anything significant that I consider negative. As per my use case, it is working fine and I have not seen a need for improvement.

I rate this product nine out of ten.

My main use case for MariaDB on CentOS in my last organization was in the telecom domain, where clients mainly focused on the database called MariaDB, for which we set up on-premises servers running on CentOS with various versions.

A specific example of how I used MariaDB on CentOS in my telecom projects is that we employed it for replication with high availability, setting up high availability for the production environment, including auto-failover and auto-switchover.

Additionally, we also used MariaDB on CentOS in the cloud environment, managing a couple of tables with terabytes of data by modifying and adding columns, new indexes, and other tasks, which were all part of my use cases.

The best features MariaDB on CentOS offers, in my experience, include high availability, which is highly compatible, such as MaxScale, along with features including auto-failover and auto-switchover.

Regarding my experience with MaxScale, we set it up for high availability in the production environment using the 2.x version and the latest version with a GUI, making it an advanced feature for high availability, especially when the master goes down, allowing the slave to take over read and write mode automatically, without any interaction or impact on the application side.

In terms of additional features such as performance and security, MariaDB on CentOS provides strong security measures, including the setup of SSL and encryption, which I have implemented in the production environment, along with more complex management features such as data encryption, TDE, and SSL.

MariaDB on CentOS has positively impacted my organization by providing more features compared to Oracle MySQL, particularly in terms of performance, advantages, and implemented features, leading to migrations from Oracle MySQL to MariaDB on CentOS.

I think MariaDB on CentOS needs improvements in some memory-level implementations within the operating system, as I have noticed issues related to memory orientation, such as out-of-memory problems.

The documentation for MariaDB on CentOS is very good. I do not think MariaDB on CentOS needs any additional improvements beyond what I have mentioned.

I have been using MariaDB on CentOS for almost nine years, working with it since version seven, eight, and now nine.

MariaDB on CentOS's scalability is impressive, as it easily handles the growth in data, users, and workload.

I have had experiences with the customer support for MariaDB on CentOS. I would rate the customer support for MariaDB on CentOS an eight.

Positive

I purchased MariaDB on CentOS through the AWS Marketplace.

I can share that after switching to MariaDB on CentOS, we saw great advantages in terms of high availability performance, particularly compared to other operating systems such as Linux and Unix platforms.

On a scale of one to ten, I would rate MariaDB on CentOS an eight. I chose an eight out of ten for MariaDB on CentOS because, as I mentioned earlier, the performance level, advantages, and features implemented in MariaDB on CentOS are well supported on the CentOS platform.

For my deployment, the cloud provider I use is AWS. I gave the overall product a rating of eight out of ten.

Regarding our use case, I find that it is quite a good database to use. It has all the MySQL features that we want, and it is quite easy to deploy as well. The whole table is in MariaDB, and that is how we use it in our day-to-day work.

In comparison to other databases, MariaDB on CentOS has most of the features that I love to use, especially considering how easy it is to use. If I compare it with PostgreSQL, PostgreSQL is quite a large database with many features. I would not say that MariaDB has everything, but it has most of the features when compared to other normal databases such as MySQL or any other small databases.

The positive impact of MariaDB on CentOS in our organization is that the overall deployment flow has been quite easier. We have MariaDB as one of the databases in our stack; we also use PostgreSQL and Redis, but MariaDB is a component in our database infrastructure. Installing it on CentOS is quite easy as well. The specific outcomes, such as faster deployment and improved performance metrics, have been quite noticeable. Earlier, we were using MySQL Lite, which, although a light database, lacked some features and performance. We found MariaDB quite performant with our applications.

Regarding MariaDB on CentOS's AI capabilities, I think its governance and security are good. The AI capabilities are good, and the guardrails are also to the point, but there is still room for improvement in the AI part.

We deploy MariaDB on CentOS in our organization using a public cloud.

I would advise others looking into using MariaDB on CentOS to give it at least a try to see how it performs in their case, as it will really be helpful for them. I do not have any additional thoughts about MariaDB on CentOS at this time. My overall review rating for this product is 7.

MariaDB on CentOS is used in a hybrid cloud and public cloud environment. It has been deployed in AWS and DigitalOcean, installed separately rather than as a managed service.

MariaDB on CentOS is almost identical to MySQL, and the experience is very similar. However, I found that MariaDB on CentOS performs better than MySQL in production. If you use MySQL, I would recommend moving to MariaDB on CentOS as it will give you better performance in production. The switch is not a big deal, but MariaDB on CentOS performs significantly better than MySQL in production environments.

I did not purchase MariaDB on CentOS on CentOS through the AWS Marketplace; I installed it separately.

I have been working for almost six months with my current company, and I have worked as a software engineer since 2007.

I do not have any specific relationship with MariaDB on CentOS other than being a customer.

Negative

I have used MySQL, MariaDB on CentOS, and PostgreSQL. When comparing MariaDB on CentOS with MySQL, I found that MariaDB on CentOS performs better than MySQL. I do not think any other database performs better than MariaDB on CentOS when compared with MySQL, which is why I give it a 10.

I have never used MariaDB on CentOS on CentOS, but I have used MariaDB on CentOS on other operating systems. I used MariaDB on CentOS mainly on Ubuntu, not on CentOS.

I believe I have covered every important aspect to discuss, and I do not have anything else to add. I was offered a gift card. My overall review rating for MariaDB on CentOS is 10.