What is your primary use case for MariaDB?

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.

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.

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.

We primarily use the solution for SaaS applications, where it is an integral part of our data management system.

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.

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.

I use MariaDB in my company to build simple web applications.

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

The solution is essentially an enterprise application. In our setup, there was a considerable amount of data being utilized. Later, the application shifted to the cloud, and for this cloud migration, we opted for a database switch from Oracle to MariaDB. That's why we migrated all the data and components to MariaDB.

I was just creating databases and doing research, basically. I've been creating new services and updating those databases in MariaDB. So, I've been learning all the SQL stuff, exploring it on my ID. This was for personal use, not for a company.

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.

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

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

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.

My company provides solutions for banks, credit card companies, and other enterprises in the financial industry.

I develop applications in my spare time. So, if the application requires a database, I use MariaDB by default.

We use several solutions for analyzing purposes including MariaDB, MongoDB, and PostgreSQL. Our use cases for MariaDB are 50% for transferring data and 50% for storage purposes.

We mostly use MariaDB on smaller systems, not for mission critical systems. For mission critical systems, we use Oracle. We're using version 10.5. The solution is deployed on-premises. We're a very centralized operation. We install the system on an application, the application runs the services, and people consume those services. We have three systems running this on the database.

MariaDB is mainly used for current applications where there are connectors already in place with CROs that create everything in the architecture.

We develop financial software such as credit management solutions for banks, financial institutions, and telcos, basically anyone who deals with credit. We are users of this product and resell to our customers. I'm the operations manager.

There are no problems with MariaDB and it works fine.

We are currently doing UAT testing with MariaDB. Production has not started. We will be using MariaDB in a complex project for the airlines.

We use MariaDB for a crypto exchange. We are currently in a test environment.

The solution is primarily a database. There are lots of telco operations coming there, including log files, operations like SMS Firewall, and lots of rules that have been passing through the database. Almost 10 terabytes of database is available in MySQL.

Our primary use cases of this solution are for emails and all the functions you would expect from a server. MariaDB is deployed on-prem, on one of our Linux servers.

The solution is primarily used to store data and for our cloud platform backend database. I use the solution for many projects.

We use MariaDB for a database.

We just used MariaDB mainly to take the place of MySQL and do some evaluation and tests in our project. It's for small business information and content management and the for workplace enterprise applications.

We're currently using it for billing.

Our clients have a variety of use cases. I'm not familiar with just one.

We are service providers and we deploy the solution for the telecommunications industry. We use the database for monitoring data that's collected on different equipment networking

We are using MariaDB for our federation of identity system, which is used to record students, service providers, and many other things. This system uses MariaDB as a database.

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

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.

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

My experience is not at the technical level, it's in the basic areas. My role regarding MariaDB is from the procurement and the technical deployment perspective. The primary use case of MariaDB is for the payroll solution, for the Columnar queries, and for the general information query on the database.

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.

The primary use case is for merging reports, merging agents, and we have implemented for business intelligence.

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.