Rails Engines Patterns
summary
Claim: Rails Engines let teams extract reusable MVC (models, views, controllers, assets, routes, rake tasks) into gems so three Rails 3 apps share a college search map and domain models with dramatic duplication reduction. The project uses a simlink workflow to avoid repeated bundle installs, pins engine versions via git refs in Gemfile, centralizes migrations in a migrations engine, and provides patterns — exposed helpers, exposed partials, extension points, configurable features — that work but add repo and release overhead versus turning the feature into a service.
AI-written summary · about
chapters (18)
- 0:00Rails Engines and monoliths
- 6:04What is a Rails Engine
- 10:16Load order and customization
- 13:46View and asset limits
- 15:33Code management with engines
- 18:25Sim linking engines
- 21:47Engines reuse and config
- 23:54Avoiding namespace clashes
- 26:25Engine patterns goals
- 27:29Pattern: common domain
- 30:24Pattern: exposed helpers
- 33:15Pattern: exposed partials
- 34:43Pattern: extension points
- 38:57Migrations in shared engines
- 42:22Pattern: configurable features
- 43:26Costs and benefits of engines
- 46:12Engines vs services trade-offs
- 49:46Summary
