MySQL

We use MySQL as the database for all of our products and websites. We have two software as a service (SaaS) products that are set up using master/slave replication and several WordPress sites that also use MySQL as a backend. We're very happy with how easy it is to set up, configure and operate MySQL databases. We use the MySQL Community Edition.

I have used MySQL for a long long time. I have used it as a student in college for my personal projects and for huge enterprise grade applications in corporate [settings]. The reason I strongly recommend MySQL over other databases is because it is open source, very very cheap and is well documented. It was an obvious choice as novice college developer then and as a seasoned developer now. It's pretty straight-forward to set up and use so it is ideal for projects with short deadlines. Also, it scales well too.

We are managing software development tasks in the cloud. The unstructured data from various sources is converted to relational mysql tables that is later used in other apps. The apps usually prefer to use data in JSON format, and we have automated scripts to convert data from these mysql tables into JSON.

MySQL is being used by the whole organization. We store enterprise reporting data.

This is used by my team for a dashboard that we created. Our whole organization was using Oracle and db2, but we started using this to create our own dashboard which will be shared with all the teams for monitoring purposes. This is very cheap and we didn't have to spend much on this and it's very easy to install and easy for us to troubleshoot issues.

The choice to use MySQL was obvious because it was open source, easily accessible and free. I needed to deliver a web app that would target a small initial audience and scale to a wider audience in a short period of time. I could have chosen other offerings but I needed to deliver this app in a short delivery window. With the help of MySQL, I was able to meet that deadline and scale the app to thousands of users. While it was eventually replaced by another application, it always ran smoothly, and never went down. MySQL will always be my first database love.

We use MySQL for our music recommendation engines, zabbix monitoring backend database, batch job management for the QA team and automatic configuration management for OrderPath. MySQL is used by our operations and engineering departments. It is a great relational database choice and is free of license cost.

We use Mysql to hold our USD data. This data is used in our final product which queries that mysql database and computes our final response. MySql provides an easy and reliable source for holding data.

I use MySQL for one of my projects as a lightweight database to capture and report data from several Excel files.

We use MySQL database as part of the integrated migration solution on the apps servers as part of migrating customer data from one billing solution to another billing solution. It is used in the client project on a customer side as part of an uprising migration framework. They were integrated with an Oracle Database at the backend to seamlessly ingest data and process and migrate millions of customers to the new transactional databases.

We have multiple projects as Masters students in Software Engineering at SJSU be in hackathons or academic projects. MySQL helps quickly deploy the database when the project demands relational schema and it's easy to use SQL queries and drivers help build high quality ACID DB instantaneously with a good DB design.

In our area we have used it on individual desktops to do prototyping when creating an oracle database may be too time consuming or cost prohibitive.

MySQL is used in our software product, along with MongoDB. Our product manages customer's business files and emails. We use MySQL to store relational data. The product is an enterprise software for the Chinese market. The product has been marketed in China for over 3 years.

We use MySQL in a variety of ways both internal to Dewpoint and among our customers:

1. It is the backend utility database for a variety of tools such as Jira, Bugzilla, NoSQL tools, etc.
2. It is an application database for some web based applications.
3. It is a caching database used at local customer sites for larger applications.
4. It is a prototyping database during initial phases of development before deploying on a more expensive RDBMS such as Oracle or SQL Server.

MySQL represents a reliable and simple database that supports standard SQL with good tools and good integration points.

We built a robust content management system with mysql with a web front end, a MAMP stack. Our design approach including writing computation-heavy parts of the application in procedures which worked very well. We used triggers to track changes and states of data points that moved between different languages and therefore had to be treated differently. We got a lot of mileage out of an open source platform. Overall, it performed very well.

A clustered MySQL instance is used as the data warehouse for a significantly large enough public ISP contract for a third party large UK phone company. This entire platform needs to be available 24/7 either to customer agents or the public for ordering services or reporting problems and MySQL is at the heart of this platform acting as the data warehouse. Equally we needed a data warehouse that could cope with the many hundreds of thousands it not millions of B2B daily transactions with up and down stream provisioning and billing systems. As always, startup and ongoing support costs are constantly questioned and using MySQL enabled us to keep these down.

We're currently using MySQL across the whole organization. MySQL stores all company data from every data source.

It is being used by several of our revenue generating products, so it is used by many teams but not the entire organization as we have other database technology that is used by other products. We like MySQL for reliability, fast data storage, scalability, querying and as a traditional database system. We use MySQL for high availability with replication.

I have used MySQL in 2 jobs previously. We had multiple clients and we used MySQL as the database to support them. In addition to that, I use MySQL for some of my side projects as well. It does a pretty good job as a relational database.

Mysql is being used across the while organization. MySQL is able to scale to our company's need, serving 10,000s of transactions per second. By adding slaves, we can quickly scale "reads" ; queries requiring to read only data vs adding data or updating / deleting existing ones.

Through an acquisition a company that used MySQL to store their data was added to our line of products. These new products continue to run on MySQL supporting very large data stores with high availability. We also have several third party and in house tools which utilize MySQL. These tools range from our production change tracking application to an Oracle supported 3rd party application with terabytes of data.

We utilize MySQL to support Healthcare systems. We use it for various reasons. We can run queries to find missing patients. We can also run queries to just run daily or weekly reports for clients. It is an everyday use for our support team. We also use and export data to show to clients.

In our company MySQL is being used by the IT department/team. We are using the community version which is free and it fulfills our needs definitely. We do not need lot of database management or users for doing several things like administration, data modeling, and generating graphics and if we did the case I would go for MS SQL server. Together I enjoy performance of MySQL as it is faster to read and write operations.

I started out using MySQL when I was first playing around with web applications that required a database back-end. It works well and is generally pretty fast. I've since switched to using PostgreSQL for most of my development, but I still use MySQL pretty heavily for a number of projects. Would definitely recommend either one as a free and powerful database server as needed, depending on your environment.
MySQL simply works and works well. It is exactly as described: a robust, relational DB which scales nicely to 100s of millions of rows. Plus, many web developers are.

MySQL is being used in our organization for storing data in a relational model and also for metadata backends for various other types of operational software. MySQL is a great choice for us due to the simplicity of the environment, the ease of use, and the low cost to operate.