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

MariaDB on CentOS is used for a company that has many applications. The company previously used Oracle and has now transitioned to MariaDB on CentOS.

Deploying MariaDB on CentOS has no complexity. However, migrating from Oracle to MariaDB on CentOS, which is for the company only and not for public access, presented many difficulties. The code formats are different between the two systems, and both functionalities are different. Many functionalities are not available in MariaDB on CentOS, so those aspects needed to be rewritten, particularly Oracle proprietary features.

MariaDB on CentOS supports JSON. MariaDB on CentOS is faster than Oracle.

Currently, it is difficult for me to assess MariaDB on CentOS's compatibility with MySQL in my systems, but it is almost similar.

I am able to hear you. You will send me a link, and I will check it.

Neutral

I work with MariaDB on CentOS, Oracle, and Postgres. CentOS is an operating system. I am working for a company that purchased MariaDB on CentOS more than four years ago. My company is not a partner, but my client is a partner.