Trailblazer: A new Architecture for Rails
summary
Trailblazer claims concrete structure: operations are the domain, controllers become tiny dispatchers that only call an operation’s process method, and models only hold associations and scopes while validation and deserialization use Reform. The demo builds a Markdown-enabled blog with nested author forms, uses Cells for view objects, persists on validate/save, and the example runs successfully. File layout groups code by feature in a concepts folder, enabling inheritance of contracts and callbacks and clear, testable separation of HTTP, validation, business logic, and persistence.
AI-written summary · about
chapters (13)
- 0:00Start
- 11:47Helpers
- 17:00Active Record
- 17:47View Models
- 20:26Business Logic
- 21:14High Level Architecture
- 23:40New File Structure
- 28:11Potential in the Future for Separating Trailblazer from Active Record
- 30:03Validations
- 30:31Active Record Methods
- 32:02Post Controller
- 37:40Inheritance
- 38:03Policies and Authentication
related talks
32mTrailblazer A New Architecture For Rails
41mTrailblazer
41mOff the Tracks - Challenging the Rails Mindset
31mIf it bleeds, it leads
01h 47mWorkshop - Applications First, Frameworks Second: Better Systems through Design
38mRails hurts, because you're using it wrong. Let's fix that
46mRails as a piece of birthday cake
31mThe History of Rails in 10 Blog Posts