MariaDB Reviews

In my work with ServiceNow, customer instances typically use MariaDB databases. As a performance engineer and tester, I focus on the application's performance and ensure its smooth integration with MariaDB. This means I'm responsible for identifying and troubleshooting any performance issues that might arise.

A relational database like MariaDB offers several advantages, including faster query execution and improved login security. Having evaluated other options like MySQL, I find MariaDB's strengths align perfectly with my specific database needs. 

MariaDB is known for its user-friendly interface and excels in specific performance areas. It delivers fast processing times, particularly for frequent select queries and insert/update operations.

We are into IoT intrusion systems. Our product is based on building automation systems. We get sensor data from across the regions. We have our own cloud hosted in GCP. The sensor data comes directly to Cassandra. We use MariaDB as a data source for UI purposes. We use a 3-node multi-master architecture using MariaDB Galera Cluster. It is deployed on Kubernetes.

The tool has good scalability and performance. The integration with other products is seamless.

MariaDB is used like any other relational database where we need complex join queries as well as tasks like read and write using the tool. The tool also offers support in terms of sharding, which is why we use MariaDB. Every time we use the tool, we have some kind of a reason, or, I would say, a requirement of asset compliance, which is atomicity, consistency, isolation, and durability, which is only provided by a relational database. Companies usually go towards open-source databases. Oracle is very costly. Oracle is not an open-source tool, which is why people tend to go towards open-source. The databases are doing pretty well in different applications.

A well-known issue for a lot of different users is associated with write-intensive applications. There are so many write-intensive applications. Usually, the applications are designed as read-intensive ones, where the number of reads is way more than the write operations. I would say MariaDB or any other relational database is designed by default to be for read-intensive applications. There are a lot of features being added to the tool, such as something called Galera Cluster, which supports write-intensive applications and sharding. People have to come up with their own way to share their applications, and that is the only way they can come up with a better performance tool for write-intensive applications.

For various applications, we use MariaDB as a database to test the incoming and outgoing data for any application. 

We check the relational database, how it's working, how the data is organized, how the queries have been written, and how we can streamline or improve the performance of these stored procedures. 

These are the things we look for to maintain a good relationship between the front end and the back end of the system.

One of the great features of MariaDB is its scalability. It's easy to handle even with large databases. 

It's also user-friendly and allows you to create complex relationships with the data. It means you can fetch data from multiple correlated or related databases in a single query. So it allows complex relationships with specific databases.

MariaDB supports SQL, and it has an advantage over regular SQL in that it is a lighter version. Even with huge amounts of data, it performs well.

We use MariaDB for small and middle-sized applications of all kinds. It is primarily used for database operations and functions as a database server.

We use some asynchronous master-slave implementations and synchronous multi-master Galera setups.

Around 90 percent of our clients are using MariaDB.

My company sells, implements, and supports ERP systems, and our particular ERP offering runs on MariaDB.

Our ERP solution runs on MariaDB by default. The second database that MariaDB also supports is not a tool we actively promote, but some of our clients prefer it and it is known as PostgreSQL.

The most valuable feature of the solution is the query speed it offers. It can really process queries, and essentially, every field that you add to a table is automatically indexed and can be queried.

I use MariaDB in my company to process the data for the database, so it is just for storage and analytics-related areas.

The most valuable features of the solution stem from the fact that it is a cloud-based tool, so it is pretty fast. The product is also considered to be an SQL-compliant solution.

We use MariaDB for industrial automation. We log some tags, and we keep the tags in the database or historical storage.

It is very simple to install, and the commands are exactly the same as MySQL.

The learning curve is small and standardized, and not anything complicated. Other than that, it isn’t much different than other solutions. It's very similar to MySQL, but a little bit more light-weighted compared to it. Unless you do a very heavy login of data, it will be fine. It is based on AWS, and MariaDB is good for certain things.