"Railways, States & Sagas: Pure Ruby for Wizards"
summary
Ruby implementation of the Saga pattern that runs as a pipeline, locks each subject to prevent parallel runs and records immutable events (action_attempt and done). Each step implements call/undo/apply methods; after a chain finishes the system rechecks external systems with apply because HTTP 200 can be misleading. Failure triggers reversed undo steps; if undo fails the item stays locked for manual retries. Prototype is extracted to a <200-line library, built over six months and then three months to tidy.
AI-written summary · about
chapters (8)
- 0:00Introduction to eBay Mac
- 1:17The saga pattern
- 2:19Implementing the orchestrator
- 3:47Handling real-world failures
- 5:34Pipeline processing mechanics
- 8:07Failure recovery strategies
- 9:41Code architecture insights
- 14:11Conclusion and wrap-up
