We are generally quite happy with MySQL, and we may have more blog articles in the future explaining some of its more advanced uses at Uber.
Why Uber Engineering switched from Postgres to MySQL
uber.com ↗·2016-07-26Wrong?
What people recommend, in their own words, with the receipt.
8 companies
We are generally quite happy with MySQL, and we may have more blog articles in the future explaining some of its more advanced uses at Uber.
Why Uber Engineering switched from Postgres to MySQL
uber.com ↗·2016-07-26Wrong?
Today, MySQL remains a core part of GitHub's infrastructure and our relational database of choice.
GitHub on MySQL as its relational database, from its MySQL 8.0 upgrade post
github.blog ↗·2023-12-07Wrong?
We started with the tech stack we were most familiar with, MySQL, and built major components separately using worker services.
Canva on starting its content usage counting service on MySQL before moving to DynamoDB and OLAP
canva.dev ↗·2024-04-12Wrong?
Because many schema changes in MySQL are blocking, the accepted workaround for many years has been to use an external tool such as pt-online-schema-change or Gh-ost .
Cash App on running schema changes against MySQL at scale
code.cash.app ↗·2023-10-23Wrong?
since a large part of our infrastructure is MySQL we need to be able to deploy these changes with a minimal amount trouble.
Booking.com on running MySQL 5.6 GTIDs across its infrastructure
medium.com ↗·2014-03-26Wrong?
We debated on using PostgreSQL, but decided to go with MySQL, again, for familiarity's sake we need to just get up and going.
Zapier on choosing MySQL over PostgreSQL for familiarity
zapier.com ↗·2012-01-27Wrong?
These are all features that vanilla MySQL cannot and does not provide.
Why PlanetScale built on Vitess
planetscale.com ↗·2021-07-20Wrong?
These include replacing MySQL replication in Espresso with Kafka-based replication, Venice and supporting the next generation of Databus (which is under development).
LinkedIn replaces MySQL replication in Espresso with Kafka
linkedin.com ↗·2016-04-19Wrong?
Every entry is a verbatim quote and a link to the public post it came from. Nothing is paraphrased. If it is not on record somewhere public, it is not here.
The verdict is what they actually said: loved and liked are explicit; recommended means they told others to get it; uses means they only say they use it; read is a book on their public shelf with no verdict; mixed and disliked are kept too.
A dashed affiliate link, sponsored or their own label means the post disclosed a relationship. It is shown, never hidden.
The small bar beside a date shows how dated a recommendation is for its kind of thing.
The bar shows how dated a recommendation is, for its kind of thing. Full and green is recent. It drains, and turns amber and then grey, as the post gets older.
What counts as old depends on the thing. A laptop praised four years ago has been replaced twice; a book loved twenty years ago is probably still loved. The bar is empty after about:
A striped bar means the post carries no date and the date shown is an estimate. No date at all, no bar.