How teams scaled Ruby on Rails: 5 real case studies
5 of the 73 engineering write-ups in our database mention Ruby on Rails in their stack. They come from 3 companies (GitHub, GitLab and Shopify) and were published between 2021 and 2024. Techniques that show up most often alongside Ruby on Rails: vertical partitioning (2). It's often paired with MySQL (2), PostgreSQL (2) and Vitess (2). Each card below links to our short summary and the original post.
How we improved push processing on GitHub
GitHub broke one huge push-processing job into smaller, independently retried jobs driven by Kafka events.
Horizontally scaling the Rails backend of Shop app with Vitess
Shopify's Shop app adopted Vitess to shard its Rails backend, covering keyspace design and the migration plan.
We are splitting our database into Main and CI
GitLab.com split CI tables into their own Postgres database to relieve its main database.
Why we spent the last month eliminating PostgreSQL subtransactions
GitLab traced replica stalls to Postgres subtransaction overflow and removed subtransactions from its code.
Partitioning GitHub's relational databases to handle scale
GitHub defined schema domains and linted cross-domain queries so it could move table groups onto separate MySQL clusters.