Structure and Chain your Poros
summary
Argues service objects (POROs) isolate business logic and act as a stable facade, shows concrete chaining pitfalls and patterns: class vs instance invocation, exception-rescue central handler, boolean-return if-else explosion, event-driven with Wisper event broadcasts that can recreate callback hell, and monadic binds that force truthy returns and make value-passing awkward. Demonstrates a real chain — convert -> extract picture -> extract translation segments — and mentions Trailblazer, Interactor and background workers as actual tools used. Claims most approaches work but chaining choice controls error visibility and complexity.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 1:14Service objects in Ruby
- 6:38Triggering actions in services
- 9:54Handling success and failure
- 16:17Chaining service objects
- 20:15Benefits of service objects
- 22:42Q&A and closing remarks
