Wrangling Large Rails Codebases

on YouTube ↗35m

" summary

Argues that large Rails apps become manageable by extracting cohesive pieces into boxes: local gems for tiny features (example: an annoyance gem with two methods) and Rails engines for larger domains (uses isolate_namespace to keep interfaces clean and migrations local). Shows a real app split into engines (teaser, publisher, show_admin), mounts them, uses vendor gems, and runs about twenty CI jobs in parallel so most specs run under a second while acceptance tests take ~16s, proving the approach works.

AI-written summary · about

" chapters (7)

1. 0:00Introduction and challenges
2. 2:16Seeking structure
3. 7:53Using gems for isolation
4. 13:31Implementing local gems
5. 17:31Advanced modularization
6. 25:21Principles of modularity
7. 27:50Q&A on testing and design

" related talks

• 33mRefactoring Towards Component-based Rails ArchitecturesStephan Hagemann · RailsConf 2014
• 41mMorning KeynoteStephan Hagemann · Birmingham on Rails 2020
• 40mMonoliths Between MicroservicesVladimir Dementyev · RailsConf 2020 CE
• 32mHow I architected my big Rails app for success!Ben Smith · Rocky Mountain Ruby 2013
• 38mAll you need is Rails (Engines): Compartmentalising your MonolithJulián Pinzón Eslava · RubyConf AU 2023
• 34m"Taming your Rails monolith"Mugurel Chirica · RubyC 2019
• 01h 28mGet started with Component-based Rails applications!Stephan Hagemann · RailsConf 2015
• 51mRails Engines PatternsAndy Maleh · RailsConf 2012