Lessons From A Rails Infrastructure Team
summary
A Rails infrastructure team describes concrete wins: supporting 400+ engineers on a monolith that grows to 4.6 million lines of code, upgrading to Ruby 3.3 and Rails 7.1 within months, and reducing average CI from 30 to 10 minutes. Tools and practices include a Buildkite Ruby DSL, incremental weekly `bundle update rails`, RuboCop rules to ban refinements, opt‑in Sorbet adoption, and a test mapping system that saves $5,000 and 68 hours in five days.
AI-written summary · about
chapters (10)
- 0:00The case for infrastructure
- 2:07Defining the infra team
- 6:53Signs and strategies
- 8:26Ecosystem and contribution
- 10:40Developer empowerment
- 13:35Incremental upgrading
- 15:40Robust CI and testing
- 18:30Optimizing CI performance
- 21:53Test mapping and speed
- 23:46Results and final thoughts
related talks
29mUpgrading Rails at Scale
35mChanging the wheels on the bus at 80 mph: Upgrading to Rails 3
32m2000 engineers, 2 millions lines of code: the history of a Rails monolith
43mThe history of a Rails monolith
28mBringing Your Rails Monolith Along As The Business Grows
36mRuby & Rails Versioning at Scale
28mRESCUE SQUAD: Rails Edition!
33mMeet Shopify's Ruby and Rails Infrastructure Team