MySQL

“Mysqldb quota/limits, fork bombs by college/school students bringing out docker environment.”

“we've been raw dogging MySQL and node.js at work for over a year”

“with 5.7 and 8.0, the advice from Percona [1], and what I've found with my own workloads, is to leave it alone”

“It is fairly standard PHP + MySQL.”

“I have a colleague that's incredibly strong with databases (we use a mix of MySQL and PostgreSQL)”

“speaking as a DBRE who has used both MySQL and Postgres, RDS and Aurora in production”

“Of course, everything has it's place and we run those too”

“I was part of a small team that built a $300M company on Ruby and MySQL that made every scaling mistake you can possibly make.”

“What I've been really looking for is a way to run SQL queries against MySQL 8.0 Inno DB without them hitting the cache.”

“we want to be able to swap between SQLite, postgres and mySQL.”

“we replaced everything acquired by Oracle to forked alternatives... we moved from MySQL to Percona MySQL.”

“We run Amazon Aurora MySQL and Amazon is finally forcing us to upgrade to 8.0.”

“in prod, we just switch to our mysql, clickhouse, redis etc cluster”

“But since we moved to Aurora MySQL, we very occasionally get stuff land in the bug tracker”

“bespoke PHP/MySQL/JavaScript that powered a bunch of client sites”

“two-way data syncing between Salesforce and MySQL via Laravel”

“We use MySQL more often than Postgres; I may take a stab at creating something similar for MySQL.”

“We run locally against MySQL and H2, and in prod against Planetscale.”

“If we could do away with ES and go back to MySQL for what are glorified data grids”

“Where I work we run a massive MySQL database that has a pretty simple sharding rule”

“We've migrated staging and testing to a DO Droplet with DO MySQl/Redis stack.”

“I grew up with MySQL, even met Monty one time at a London meetup”

“The only reason we haven't gone Postgres is because our codebase is extremely extensive and dependent on MySQL/Maria.”

“since amazon natively supports mysql on aurora we didn't have to worry about compatibility.”

“back when we switched databases from mysql to postgresql. It would fire up a mysql based database”

“We used this to great effect at Facebook for MySQL backups in the early 2010s.”

“we run MySQL, ClickHouse, and Prometheus to manage our own SaaS platform for ClickHouse.”

“If your app can be powered by a single mysql instance, _just do it_.”

“My mid-sized shop uses managed offerings for MySQL and Postgres but we run several stateful workloads”

“developers don't need to have MySQL installed on their machines”

“We had a UTF-8-configured table in MySQL (we also discovered in the project, that MySQL can have encodings set differently per-table”

“I moved to PG from MySQL in 2014 and don't regret it since.”

“I've only been using PostgreSQL for the last 20 years, and before that MySQL.”

“we'd already migrated to MySQL for many of the workloads because the database was having at best 95% reliability”

“Same goes for MySQL... I tend to end up sticking with tried and true relational DBs.”

“For awhile, we were storing this in a (very large) MySQL database, sharded with Vitess.”

“I have done things in MySQL v3 in 2006 that should not be done with a modern database even today (a taxonomy search engine 3 levels deep.”

“I've managed shards/clusters of Postgres and MySQL in my life”

“I've since ported a few apps in early development or production between Microsoft SQL server, MySQL and Postgres”

“are backed by mysql and redis, etc.”

“Locally, docker compose will spin up N mysql instances and relevant services under test.”

“I've only ever seen PostgreSQL/MySQL/MariaDB/Oracle be deployed successfully as single instances in prod that are scaled vertically”

“We switched to a separate service for generating tweet IDs (instead of MySQL sequences)”

“RDS (MySQL or PostgreSQL), ES (OpenDistro), S3 (Minio), and SES”

“our MySQL is configured with 151 max connections”

“Aurora/MySqL (OLTP RDMS).”

“We use in-memory sqlite databases for unit testing a MySQL backed web service.”

“the central MySQL databases with profile and post information; not media or messages.”

“when restoring very large databases we need to use MySQL in a real VM instead of in our Docker setup”

“Zulip was originally developed with MySQL, and then about a year into developed we switched to Postgres”

“so each customer had their MySQL DB for it.”

“we are also able to run our software during development pointing to locally installed open-source versions of MySQL just fine.”

“we switched from doing exercises in MySQL to PostgreSQL when recursion came up”

“having converted from MySQL and never looked back”

“we were a big Perl Apache and MySQL shop.”

“It's admittedly been a long time since I've used MySQL for anything significant”

“In my experience this is rare... Additionally, DDL in MySQL 8.0 is now atomic.”

“we use an ETL script to suck all our Google sheets into MySQL then we run queries for reporting.”

“I recently migrated a small side project from MySQL to PostgreSQL.”

“We actually built a data lake (with Python and MySQL)”

“running on AWS Aurora MySQL. ... We've had very few issues with this part of our codebase.”

“OS X still has a way better free MySQL client in the form of Sequel Pro”

“We run our own DNS nameservers (using PowerDNS and a single MySQL node”

“things sitting behind rancher, postgres, mysql”

“I have used MSSQL, MySQL, PostgreSQL, Mongo and Cassandra all as primary data stores.”

“PHP/MySQL backend (legacy) with our own home-baked framework”

“Goober had the idea of storing pictures in said MySQL database. 70 GB of pics...”

“we had issues with 0000-00-00 dates that are valid in mysql but not in postgres.”

“Twitter's original (acquired via summize) search was written in mysql.”

“We migrated from MySQL 4.6, that's why our tables are in fact MyISAM.”

“we use a docker-compose file to start an official mySQL image and the local rails repo.”

“we do something very similar for MySQL with MHA.”

“so I switched to manually writing mysql queries, but not the ideal”

“launches all services required (e.g. apache, mysql, sshd, elasticsearch) by running "service XYZ start"”

“log it to the MySQL and ensure it reports to the manager where the user stopped on the form”

“We run MySQL on product and am in the process of de-normalizing it.”

“We run our own MySQL and Redis on an Ec2 instance.”

“I've been using docker in production with Elasticsearch and MySQL for 3 years in the PB scale”

“I have run PostgreSQL, MySQL, and SQL Server in production on large workloads”

“with the experimental, now-deprecated MySQL backend enabled”

“have our data services (Elasticsearch, Cassandra, MySQL, MongoDB) join the rest of our apps on Kube-orchestrated infrastructure”

“Been using gorp over the past month to prototype MySQL database schema and insert strategies for a performance system”

“I opted for PHP/MySQL, and development time felt like lightning.”

“We also use it against mysql. Annoyingly there is no driver for that so we had to build a nasty layer than translates from influx to mysql.”

“In my experience it's generally safe to upgrade across post-GA point releases of the same major version”

“We run a fairly standard java/MySQL web app, with paid silver support.”

“Wrote 150 lines of parsing csv and MySQL inserts and it took about the 4 hours I was sitting around”

“At YouTube, we run our main MySQL databases (the ones with tables for users, videos, views, etc) inside containers with local storage.”

“We run LAMP (Linux-Apache-MySQL-PHP) stacks on virtual machine instances on servers worldwide of our choosing.”

“OP's company thought using mySQL was a good idea, but maybe someday, nights will not be long enough for batches to run.”

“We do this for all of our services: mysql, redis, sphinx, the web app itself”

“For our few services that run on MySQL, I'm really hanging out for MariaDB”

“Having moved from Mysql to Postgresql in 2005 and continued with it up to the present”

“We had to change a few things moving from mySQL to Postgres.”

“we run MYSQL RDS in production with two AZ enabled, we pay x2 the prices”

“At work we run a large mix of Windows Servers, SQL servers, Linux, Drupal, MySQL, Moodle etc.”

“I generally use MySQL or PostgreSQL on RDS (AWS) given DBA's are hard to find.”

“Your MySQL-as-a-service is abysmal. It's running 5.1 (Do you have any idea how old that is?)”

“we're using MySQL as the database (though we will likely move to PostgreSQL in the future)”

“From personal experience, I've used "ON DUPLICATE", but we ended up dumping it and making our API better/more secure. This was even before we switched to Postgres.”

“How to manage a mysql server cluster.”

“now we just use Postgres, MySQL, MongoDB, etc. etc.”

“caches products in a JPA-accessed MySQL database.”

“sometimes MySQL as localhost”

“it's just as easy for me as MySQL was for the same sort of things”

“Recently upgraded from MySQL 5.1 -> MariaDB 5.5 with no issues what so ever.”

“I have not experienced any compatibility issues with MariaDB vs. MySQL.”

“So I run two instances of mysql, one is PROD and the other is read only replication.”

“We use linux for: redis, elasticsearch, HAProxy, DNS (bind), nginx, mail (exim) apache, wordpress, mysql, nexpose, backups, puppet, asterix, android builds and our internal mercurial.”

“those of us who used sqlite could not migrate to mysql when sqlite was dropped.”

“we use this for our production MySQL stuff”

“some NFS and MySQL slaves that function as snapshot/backup hosts only.”

“makes it easy to batch everything up and push it into MySQL at the end of the day.”

“SET GLOBAL read_only=1 only affects new connections.”

“mysql_role_swap is not black magic, it doesn't do automatic failover, it doesn't run in the background / daemonize itself.”

“At my current job we use PostgreSQL and MySQL in production, and H2 in development.”

“we have a few legacy projects still using MySQL that we haven't bothered migrating.”

“We use MySQL exclusively, unless a client forces us into MsSQL/IIS.”

“where I currently work we use a ton of Cassandra, Redis, and very little MySQL on the side”

“The application currently uses standard MySQL 5 with Innodb, and going with Galera would mean that no code change would be necessary.”

“we've had this same experience with every database technology we use - including MySQL and Redis.”

“Is there any close equivalent for mysql, which we use at $work?”

“Our DBAs tried to convince us to switch from MySQL to Maria a few months ago.”

“We do use some performance related settings related to this as well: innodb_flush_method = O_DIRECT”

“I cut my DB teeth on Oracle and mysql”

“some workers just dropped dead saying MySQL couldn't answer”

“I've been using a lot of MySQL and some NoSQL solutions over the years.”

“we aren't using any external frameworks - just Tomcat and MySQL”

“It had MySQL with a prod snapshot, RabbitMQ, a Django web app and a bunch of twisted services.”

“we migrated over from a custom queue on top of MySQL”

“Despite a desire to use Postgres, we use MySQL in production. MySQL is what I knew and thus still what I know.”

“we run a very straight forward Rails hosting stack (Apache/Passenger/MySQL)”

“We run all of our MySQL and Mongo slave servers with local RAID-0 ephemeral storage.”

“MySQL is what we started with, as time has gone by, we've migrated more and more data to other data stores.”

“on some very busy MySQL servers.”

“the other is a rewrite of something we used to use MySQL for.”

“I'm currently working on a set of SOAP web services using tomcat, cxf, mysql, and hibernate among others.”

“At Posterous we use MySQL as a main data store but MongoDB for simple analytics and Redis for set operations around contacts and subscriptions.”

“I've been using sphinx for georanking, on top of mysql. Works really well.”

“I've been using either MySQL with Sphinx or MongoDB with the built-in geonear successfully.”

“I've only been with companies that had MySQL installations (Facebook and Twitter)”

“We switched from Apache to nginx and are now running in a full MySQL / python / fcgi / nginx / memcached environment.”

“I wrote a medium-sized online game for a guy who wanted to do it in Mono/MySQL.”

“we've switched from MySQL to Google AppEngine (and BigTable)”

“Database servers work in teams of 3, with master-master replication and then a slave.”

“Occasionally, we run into limitations of MySQL.”