We use multiple models here because we do full development. What we deploy on MySQL is from the Helm chart or it's a Dockerized deployment of MySQL. So we're using the Helm stable chart right now. That's sort of the easiest way to deploy it - to say just one command and it bootstraps your whole database within your classical means or cluster. You can do it locally with mini-crews or developers, for organizational use, or Kubernetes. It's single-node Kubernetes.

Also, you can just deploy MySQL locally with a Helm chart. Regarding production, we have a kind of automated process which is similar to what Spinnaker deploys, with a Helm chart as well as within the cluster. Some other solutions we don't run within the cluster, we use the Cloud version of the database which is Cloud SQL, Google Cloud, and AWS. Those are fully managed ones, of which there are two versions. We have our self-managed version which we run locally and with our DEV cluster and then there is production, as well.

We also use a self-managed version since every cloud provider offers MySQL, even AWS. It depends on the client's needs, how flexible the client is, and also how comfortable they are with MySQL.

We either go with our managed version or the Cloud version. Both are supported because today the Mica server that's actually accessing the database or the piece of software just needs a connection string, it doesn't care if it's running within the Synchronous Cloud. If it's running somewhere else in the Cloud, it's still a private connection on the same network.

So the only differences here are in terms of money costs and whether it's managed or not managed. So for local development, you don't want to have a managed database in the Cloud. You don't need to be tethered to the Cloud, you'd rather just deploy locally. And because we have the same deployment scripts that run locally in DEV and testing, we use the same Helm chart and the same Docker version with MySQL to distribute that through our DEV environment to test the bills and run the test and there is a full QA environment for teaching, as well.

The solution is a database server. You can use it for desktop or web applications. The tool is used mostly for web applications. Most websites have MySQL databases behind them.

Mostly, we're using it as a database behind a machine learning application.

Below are a few instances where MySQL is utilized. Typically, I have worked on RPA projects. To preserve or update data from the database, I must create a database and data tables, which can be used again in the future or by other processes. Additionally, the data can be shared. I need to store and manage the data for reporting and management purposes.

The tasks I perform, mostly involve sorting, patching, and maintaining data, as well as creating stored procedures.

We are developers working on different types of projects. We use relational databases in some projects and non-relational databases in others. When we use relational databases, we use MySQL. When we use non-relational databases, we use our DynamoDB or MongoDB.

We use it to meet the requirements of our customers while optimizing performance and reliability within the constraints provided.

We use it for building web applications and managing data.

We use MySQL for OLTP applications. HeatWave is used more on the SnowFlake and DSS side of the application.

Our primary use case for MySQL is for our internally-built system. When our developers are doing the assistance, usually we provision them with the MySQL driver.

MySQL is an open-source relational database management system used to store data.

Our company uses the solution to extract data from databases. We perform the create, read, write, and operations in databases.  

The number of users depends on the project. If there is a demand, then people good with SQL will jump in on projects. 

I used it for a small customer database company in England with 20 employees. They didn't have that much data, and we needed something easy to install and easy to run. This was my use case for it.

I use the solution for personal use cases like software development, mostly database bug systems.

I've used MySQL in the past for a variety of tasks. 

I once used MySQL when I created a PostgreSQL database for club management tasks. This included handling registrations, events, and mailing notifications for payments and event details. It served as a source service provider.

My primary use case for MySQL is with my products or websites for clients, and it helps me maintain relations with the best.

We use the product for database management, as a database engine.

We use MySQL to manage business intelligence reports by linking them with Oracle database and Power BI. 

The primary use case for MySQL is to develop web applications, proof of concept projects with data collection, data manipulation, and data reporting on both Windows and Linux platforms. 

We also use MySQL to store the data that we receive from different projects and build data models. We can also develop reports out of it.

MySQL is used for small application use only and not used for enterprise-level business applications.

MSQL is free open-source software. This is the most valuable aspect for any company as it helps to reduce the cost.

Our organization uses MySQL as an ERP database for transactional and financial systems.

We're on a software development team. We develop applications.

We're currently running version 5.7 of MySQL, and we are going to be upgrading to version 8 this year.

MySQL server currently is in a co-location center. We've got a hosting provider that takes care of that for us. We are looking at moving it into AWS, but that won't happen this year. We do have a smaller MySQL RDS instance in AWS right now, but it is pretty minimal. 

We use the tool in projects with customer records in the database. There will be a front-end application to search and find specific data from the tool. In another project, there are product listings, and the front end fetches data from the tool and shows it in a gallery or list view on the web page or mobile application.

We have used the solution to manage database administration and custom attributes.

My daily tasks are related to data mining and TBICO Spotfire is one of the products that I use. We are a small group of geologists operating in a niche area who are analyzing geochemical data. Our backend database is MySQL and we use products such as Power BI, Tableau, and Spotfire to display data for the geochemists.

I perform data-related tasks such as data manipulation and creating views, then updating the database afterward, all using SQL queries. As part of this, I'm making entries as needed or corrections to data that has already been processed.

I don't use MySQL extensively, but I use the code within MySQL for preparing some reports and all that.

We are primarily using it as a database for our products. For internally built systems, we have MySQL. We use it internally.

I am using MySQL for business data queries.

It's been used as a primary relational database for most applications. It's scalable and could easily be maintained and could be migrated to any Cloud-based Database as a Service solutions which are compatible with MySQL.e.g. AWS RDS MySQL, AWS RDS Aurora, Google SQL. 

We sell MySQL to customers who need to build second tier applications, not their core application. For some of our customers, when they are planning to build their second tier application, they will choose MySQL rather than Oracle which is more expensive.

Used as a data store for RESTful web services and other web applications. Was deployed to store RSS feeds, and for 100 joomla instances. 

I started to use MySQL at some point when I had some issues that I couldn't get around. I normally use the tool in professional opportunities and when I require support from MySQL.

Cacti is a tool for monitoring devices on a network in graphical terms, for which it uses MySQL or MariaDB. I mostly deploy Cacti with MySQL or MariaDB. Somewhere down the line, I started to have some issues with the permissions in MySQL, including its areas like superuser privileges and similar stuff, which took me a while to figure out. I think the tool is fine for me now.

We use MySQL for customer management authentication in our company.

Our primary use case for this solution is a home database of payments.

I used MySQL for academic purposes. I use it for learning purposes.

You can start anything with MySQL.

You can build your own app, and store your data.

It's a free solution for development purposes.

We primarily use the solution for the many small applications we use. However, we do not use it with our enterprise-level applications.

The solution is primarily used for mobile applications and IoT-based services. It's a good choice for development. 

I'm using it to create a small database for a project that I'm working on.

We are using MySQL for backend operations since we are a software backend developer. We are using this tool in our backend application for acquiring the data.

We mainly use MySQL for our Relational Database Management System(RDBMS). We are maintaining our customer data in a defined way. We have to create various schema levels. We are presenting the customer data, such as name, mobile number, what was purchased, and what they like or dislike. Once we create the schema, a set of data, we need to maintain the unique constraints.

For example, for customers, we'll assign a unique ID to each record, that will be a primary key. All these SQL constraints we'll use and there should no variance or replication of data isolated. When we perform any update operations, it should not affect any of the data isolated. 

We need to take care of many things, such as consistency, isolation, and variability for constructing any database. There are a few more concepts as well, such as normalization and PL/SQL. For example, if I want to run a job at a particular time, the product will use PL/SQL. We are like implementing our coding skills to databases.

Our operations are on-premise. However, we are in the process of moving everything to the cloud.

Our primary use case for MySQL is for running applications on our Linux boxes. We have very few applications that run online, but we use MySQL on those boxes, primarily for our email system. We haven't considered working on cloud, so all our solutions are on-premises. 

It is an ideal database to use online learning environments and SMEs. It works well with  Moodle, the open-source learning solution, and is the defacto standard for that product as Moodle is written in PHP which generally goes hand-in-hand with MySQL. As it is an open-source and free solution it is an economical method of storing important companies or small business data. At the same time, it offers a rich set of functions comparable to other large-scale enterprise solutions such as SQL Server and Oracle. 

We use MySQL for storing data on the web server. It is a competitor of Apache. The solution can also be used for analytics, warehousing, and Big Data.

We developed a network monitoring software and used MySQL as a backend database.

We utilized the two most common and popular MySQL database engines, MyISAM and InnoDB.

We store collected monitoring data and configuration data on MySQL. Also, our network monitoring solution reporting module is based on the MySQL MyISAM database engine.

We use both Windows and Linux versions of MySQL, and we utilize the backup and recovery features.

To summarize, our primary use case is the embedded DB component for our network management software.

Our main use case for MySQL is for applications and seamless migration to the DR site. And the application in this case is an airport application.

I have been working for 25 to 30 years in this domain, and during this time, I have used various products such as MySQL, SQL Server, and PostgreSQL. Currently, in my product, I am using PostgreSQL, and in some projects, I am using MySQL. We are using the latest version of this solution.

We do projects for various government departments. We have used this solution for the transport department for vehicle registration, driving license, and all such things. We have also used it for port projects, depots, educational counseling projects, school databases, higher education, and health registry. As an organization, we have a lot of use cases of this solution.

We primarily use the solution for NDB and CG clusters.

We primarily use the product for small applications.

We use this solution for the database.

I am a senior manager of the infrastructure team and MySQL is one of the products that I work with. We use it in an e-commerce portal. The database is light and everything works smoothly.

We use MySQL as a light database engine to provide database service to our web application. 

Almost all of our software engineers use MySQL.

We want to continue using MySQL but it merged with Oracle and the scalage changed. After they merged, we tried MariaDB. 

For two years, we tried MongoDB and prepared for application migration; all because the scalability changed when MySQL merged with Oracle. 

MYSQL is our main database. We use it for every project.

I use it for storage procedures, SQL administration, and database administration.

We also use it for the development of reports, and projects that are deployed for our customers. It is also used to develop applications.

The majority of companies use it for their development projects.

We're using MySQL for data warehousing and logging.

We are using it for RADIUS protocol, which is for network access. We are tracking the duration of user stations.

I use the product as a backend to my application.

We use it for my clients. Basically any website that uses WordPress uses MySQL, so we use that to manage and run our WordPress websites. Some we have on a cloud, some we have at hosted servers.

It is part of WordPress and some clients are using it for eCommerce, and others are just using it as part of the website to give information.

We use the solution for our applications, as a management system. We utilize it as an operator or relational database. 

In our company, we are providing an application in PHP language and we need to use another database and we made the decision to use MySQL.

We are interfacing it with MicroStrategy. There are ODBC connections. We have 10 to 12 users in our company.

We are assessing the possibilities of moving to the cloud. We are not yet sure if we are going to move to the cloud.

With most open source products we were building, even the language was open source, such as that which employs PHP. This is where the MySQL free version was being primarily used by many of the clients in the storing of their data. 

There have been some great shoppers which we built with the solution. We use the solution to store the transactional data that we receive from various sites or have the data stored in MySQL. 

I use MySQL as middleware to get the extracted data from the database. I work with MySQL as an administrator to set up the whole platform. And I document the recipe for setting up the MySQL database.

We are working with the latest version.

We are doing POCs for our clients in our testing lab, and if a POC is working fine, then we give it for the production release. 

We use it for financial transactions such as money remittance.

We only support the backend and only carry it as a database. You can do what you want on the database to create the schema and to manage the rest of the organization.

The primary use case is as a reporting solution, data collection, data manipulation, and similar tasks. We install MySQL on Linux and Windows machines for testing our enterprise application.

We are a solution provider and this product is part of our offering to our clients.

Small to medium-sized business usage. The main advantage is the very large user base. This enables users to fix about any issue by answering any question. From a technical viewpoint, MySQL is on par with the other open source database solutions.

We use MySQL for internet applications. 

It is deployed on local servers, and we are using version 8. The whole company uses our database. Our users don't communicate with the database directly. They use a web interface. All programs are deployed using MySQL. We have hundreds of thousands of users accessing MySQL via the website. Two of us manage the database, but it's enough for only one person to manage daily operations. 

I'm not involved from the database side as much. I primarily use it for reviewing the data structure as the architecture before I build a data model in our BI tools.

General querying is pretty much what I do, and also analyzing data types and data structures within the database itself. I review the data structure within them. And I use that to build the data model, which we have in our reporting environment. That's primarily all I use it for.

We are an IT services provider, so the solution is for our customers. I can't answer for the customers in terms of how they use it. 

Typically, customers are running applications that need to connect MySQL and to store some of the data.

We are basically using it for our applications.

I do not recall which version I am using. 

Although we do not use it for the main core system, the solution acts as a database which is useful for login applications, data warehousing. 

We store mostly the metadata-related information and that's our primary use case for MySQL, storing a transactional database. 

We are an asset management product company. Our product is deployed on the cloud and the backend database for it is MySQL.

The main reason that customers pick MySQL is that it's cost-efficient.

Primary DBMS solution for web apps developed on either ASP.NET MVC or Zend / PHP for customers.

The community version of MySQL only offers simple backup and restore tools, but it is OK for many web dev projects for customers that want a low budget solution.

I have used the solution for a database tied to application development.

I'm currently using MySQL for the contact center database, and it is in the cloud. I have also used it in other projects for database and CRM, and it was on-premises. I have used it in 20 projects.

We utilize the DB as a data-repository solution for our front-end applications. The solution gives us the ability to run numerous instances on various geographical cloud servers.

I'm a tester, an optimization tester. It's basically when the developers have the back-end in SQL. We go and test it out for them and check that the table updated correctly, and we do something on the front-end.

I use MySQL to teach students about databases. They implement projects using this product.

We are currently using the 6.8 version and, prior to this, used the 5.3. I use the updated versions.

We are using this solution for database management.

I started an Azure account and this is when I tried testing different databases, non-relational databases, and relational databases, using this solution.

I used it to obtain insight into the entire network and the resources being utilized. The current GUI lets us see the traffic happening east to west and the total bandwidth consumed by it.

We use MySQL primarily for internal application systems that we developed.

We use MySQL to store data for our customers, in the database. It is a service-related application. Also to configure the data.

We use this solution for billing, accounting, and data analysis.

I use MySQL for employee service in an OLTP database.

It is the database for a web application. I am using it for personal and official purposes.

We use MySQL and MariaDB for most part of our mission critical applications

This as it is so simple to integrate with web applications, and other well known applications.

We use MySQL to organize data, analyze information, and make decisions for the company. We also use it to process information from different areas in the company.