Beyond the service object
summary
Claims that moving controller business logic into a dedicated operation class makes unit testing and reuse trivial, shows a DSL that breaks logic into named steps and uses the railway pattern for automatic control flow, compares Trailblazer to dry‑monads and Interactor, and reports tracing that saved weeks of debugging by showing which step and context failed. Demonstrates nesting of operations, a context/result object passed step to step, and modeling long running processes with BPMN workflows and interactive tracing that prints clickable traces.
AI-written summary · about
chapters (11)
- 0:00Introduction and setup
- 1:08What is abstraction
- 7:18Service objects and business logic
- 11:30Rails business logic problems
- 14:01Personal journey and cells
- 20:43Trailblazer operations concept
- 26:40Railway pattern in Trailblazer
- 30:14Comparing service object gems
- 34:30Trailblazer Pro and advanced features
- 38:01BPMN workflows in Trailblazer
- 39:49Conclusion and call to action
