|
| 1 | +--- |
| 2 | +title: "MySQL Adopters" |
| 3 | +url: "/member-directory/adopters/" |
| 4 | +description: "Organizations that run MySQL in production — each one backed by a public source: an engineering blog, a conference talk, or a case study." |
| 5 | +layout: adopters |
| 6 | +subcategories: |
| 7 | +- Adopters |
| 8 | +adopters: |
| 9 | +- company: "Airbnb" |
| 10 | + industry: "Travel marketplace" |
| 11 | + use_case: "Core databases on Aurora MySQL; MySQL replication used to partition the main database" |
| 12 | + reference: "MySQL customer page" |
| 13 | + url: "https://www.mysql.com/customers/view/?id=1271" |
| 14 | +- company: "Backblaze" |
| 15 | + industry: "Cloud storage" |
| 16 | + use_case: "Runs Vitess (sharded MySQL) in production" |
| 17 | + reference: "KubeCon NA 2024 talk" |
| 18 | + url: "https://kccncna2024.sched.com/event/1hoxf/vitess-introduction-new-features-and-running-in-production-deepthi-sigireddi-planetscale-derek-perkins-nozzle-sudhi-vijayakumar-backblaze" |
| 19 | +- company: "Booking.com" |
| 20 | + industry: "Travel" |
| 21 | + use_case: "Main relational datastore: thousands of servers in 200+ clusters, 20+ years on MySQL" |
| 22 | + reference: "MySQL Global Forum 2025 slides" |
| 23 | + url: "https://downloads.mysql.com/events/mysql-global-forum/20_Years_of_Operating_and_Scaling_MySQL_at_Booking.com.pdf" |
| 24 | +- company: "Cash App (Block)" |
| 25 | + industry: "Fintech" |
| 26 | + use_case: "Started on a single MySQL database, scaled out with Vitess" |
| 27 | + reference: "Cash App blog" |
| 28 | + url: "https://code.cash.app/sharding-cash" |
| 29 | +- company: "Dropbox" |
| 30 | + industry: "Cloud storage" |
| 31 | + use_case: "Edgestore metadata store on thousands of MySQL shards" |
| 32 | + reference: "Dropbox Tech blog" |
| 33 | + url: "https://dropbox.tech/infrastructure/reintroducing-edgestore" |
| 34 | +- company: "Etsy" |
| 35 | + industry: "E-commerce" |
| 36 | + use_case: "~1,000 MySQL shards (425 TB), migrated to Vitess" |
| 37 | + reference: "InfoQ, Apr 2026" |
| 38 | + url: "https://www.infoq.com/news/2026/04/etsy-vitess-sharding-migration/" |
| 39 | +- company: "GitHub" |
| 40 | + industry: "Developer platform" |
| 41 | + use_case: "Primary datastore for metadata (issues, PRs, comments); fleet upgraded to MySQL 8.0" |
| 42 | + reference: "GitHub Blog" |
| 43 | + url: "https://github.blog/engineering/infrastructure/upgrading-github-com-to-mysql-8-0/" |
| 44 | +- company: "HubSpot" |
| 45 | + industry: "SaaS / CRM" |
| 46 | + use_case: "MySQL on Vitess and Kubernetes" |
| 47 | + reference: "CNCF case study" |
| 48 | + url: "https://www.cncf.io/case-studies/hubspot/" |
| 49 | +- company: "Intercom" |
| 50 | + industry: "SaaS / customer service" |
| 51 | + use_case: "MySQL is the primary datastore; moving from Aurora to Vitess on PlanetScale" |
| 52 | + reference: "Intercom blog" |
| 53 | + url: "https://www.intercom.com/blog/evolving-intercoms-database-infrastructure-lessons-and-progress/" |
| 54 | +- company: "Meta" |
| 55 | + industry: "Social media" |
| 56 | + use_case: "Social graph tier (UDB) on MySQL with the MyRocks engine" |
| 57 | + reference: "Engineering at Meta" |
| 58 | + url: "https://engineering.fb.com/2017/09/25/core-data/migrating-a-database-from-innodb-to-myrocks/" |
| 59 | +- company: "Nozzle" |
| 60 | + industry: "SEO analytics" |
| 61 | + use_case: "Vitess on Kubernetes; founder is a Vitess maintainer" |
| 62 | + reference: "KubeCon NA 2024 talk" |
| 63 | + url: "https://kccncna2024.sched.com/event/1hoxf/vitess-introduction-new-features-and-running-in-production-deepthi-sigireddi-planetscale-derek-perkins-nozzle-sudhi-vijayakumar-backblaze" |
| 64 | +- company: "Pinterest" |
| 65 | + industry: "Social media" |
| 66 | + use_case: "Sharded MySQL as the core store for pins, boards and users" |
| 67 | + reference: "High Scalability" |
| 68 | + url: "https://highscalability.com/scaling-pinterest-from-0-to-10s-of-billions-of-page-views-a/" |
| 69 | +- company: "Pipedrive" |
| 70 | + industry: "SaaS / CRM" |
| 71 | + use_case: "Schema-per-customer sharded MySQL plus microservice databases" |
| 72 | + reference: "Pipedrive R&D blog" |
| 73 | + url: "https://medium.com/pipedrive-engineering/database-engineering-in-pipedrive-an-overview-315b40d05282" |
| 74 | +- company: "Shopify" |
| 75 | + industry: "E-commerce" |
| 76 | + use_case: "Every shop's data in MySQL shards inside isolated pods" |
| 77 | + reference: "Shopify Engineering" |
| 78 | + url: "https://shopify.engineering/mysql-database-shard-balancing-terabyte-scale" |
| 79 | +- company: "Slack" |
| 80 | + industry: "Workplace communication" |
| 81 | + use_case: "All data on MySQL since day one; Vitess serves 99% of query load" |
| 82 | + reference: "Slack Engineering" |
| 83 | + url: "https://slack.engineering/scaling-datastores-at-slack-with-vitess/" |
| 84 | +- company: "Twitter / X" |
| 85 | + industry: "Social media" |
| 86 | + use_case: "MySQL behind tweets, timelines and user data; moved from in-house fork to community MySQL 5.7" |
| 87 | + reference: "SiliconANGLE, 2012" |
| 88 | + url: "https://siliconangle.com/2012/04/09/twitter-open-sources-its-secret-mysql-hacks/" |
| 89 | +- company: "Uber" |
| 90 | + industry: "Mobility" |
| 91 | + use_case: "Schemaless trip datastore built on sharded MySQL" |
| 92 | + reference: "Uber Engineering" |
| 93 | + url: "https://www.uber.com/blog/schemaless-part-one-mysql-datastore/" |
| 94 | +- company: "Wix" |
| 95 | + industry: "Website builder" |
| 96 | + use_case: "MySQL as default engine, including as a key/value store" |
| 97 | + reference: "Wix Engineering" |
| 98 | + url: "https://www.wix.engineering/post/scaling-to-100m-mysql-is-a-better-nosql" |
| 99 | +- company: "Yelp" |
| 100 | + industry: "Local reviews" |
| 101 | + use_case: "Nearly all data in MySQL (Percona Server), functionally sharded" |
| 102 | + reference: "Yelp Engineering" |
| 103 | + url: "https://engineeringblog.yelp.com/2015/01/mysql-at-yelp.html" |
| 104 | +- company: "YouTube" |
| 105 | + industry: "Video streaming" |
| 106 | + use_case: "Video metadata on sharded MySQL; Vitess was built here" |
| 107 | + reference: "Vitess history" |
| 108 | + url: "https://vitess.io/docs/overview/history/" |
| 109 | +- company: "Zendesk" |
| 110 | + industry: "SaaS / customer service" |
| 111 | + use_case: "Aurora MySQL + S3 tiered storage for event data" |
| 112 | + reference: "InfoQ, Dec 2023" |
| 113 | + url: "https://www.infoq.com/news/2023/12/zendesk-dynamodb-mysql-s3-cost/" |
| 114 | +--- |
0 commit comments