Keeping the Rails Magic Alive After 18 Years
summary
Eighteen years of a Rails app started in 2007 grows to 3 million lines and the team migrates toward a Component Based Rails Application using Cobra while still running Packwerk checks, claiming build times drop from 4.5 hours to roughly 90% faster and a 50% win by splitting models into components. Built replacements include a recruiting app and Connect messaging on Matrix and even an inhouse cloud. Open source tools mentioned are cobra_commander, edge_stitch for per‑component schemas, Playbook Design System and consent for dynamic permissions.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:12Power Home Remodeling and Nitro
- 3:23Nitro origins and Rails growth
- 5:08Power’s build versus buy policy
- 8:21Custom-built systems at Power
- 11:12Power’s own infrastructure
- 12:15Challenges of a Rails monolith
- 13:39Modularizing Nitro with Cobra and Packwork
- 16:48Component-based Rails commitment
- 17:50First steps in modularization
- 18:54Faster builds and testing
- 20:17Cobra versus Packwork
- 21:00Open source component tools
- 22:06Edge Stitch and schema management
- 23:10Dynamic authorization systems
- 24:10Playbook design system
- 25:14Open source and closing
related talks
33mRefactoring Towards Component-based Rails Architectures
28mBringing Your Rails Monolith Along As The Business Grows
32mBuilding HUGE Web Apps: Rails at 1,000,000 Lines of Code
32m2000 engineers, 2 millions lines of code: the history of a Rails monolith
23mCrafting Rails Culture
34mIndustrial Rails
32mHow I architected my big Rails app for success!
33mRails APIs: The Next Generation