Building HUGE Web Apps: Rails at 1,000,000 Lines of Code
summary
A Rails app grows past over a million lines and still ships features by focusing on restraint: fix n+1 queries, push work into background jobs, and prefer simple MVC over premature abstractions. Deploy tooling lets teams do 4–5 deploys per day (Slack-triggered pipelines). Use third‑party services sparingly—LaunchDarkly feature flags, Pusher, Twilio, New Relic are in use—train everyone on SQL and domain rules, give small squads autonomy, and add complexity only when necessary.
AI-written summary · about
chapters (24)
- 0:00Introduction and setup
- 1:03Key to building huge apps
- 3:28Contrasting experiences at two companies
- 5:54What makes the difference
- 7:18Technical strategies for scale
- 9:06Embrace background jobs
- 10:33Manage dependencies carefully
- 11:18Skepticism toward abstraction
- 13:03Avoid over-modularity
- 14:05Leverage third-party services
- 15:11Feature flags for control
- 16:13Use database power effectively
- 17:36Database design matters
- 18:39Process and team autonomy
- 21:52Squad-based development
- 22:56Flexibility over rigid rules
- 24:03Invest in deployment tooling
- 26:29Simple processes that scale
- 27:33Encourage team autonomy
- 28:16Tooling for high-scale migrations
- 28:36Domain expertise and training
- 29:38Encourage cross-technology growth
- 30:20People and ownership drive success
- 31:03Customer feedback and change
