Separating Your Concerns With the Solidus Event System
summary
Claims that the Solidus event system decouples side effects from core logic and makes extensions testable and maintainable, demonstrating actual examples: built a cart_updated custom event and uses built‑in order_recalculated and order_finalized events, shows payload design (order and boolean result), tests with current ActiveSupport::Notifications and notes the new custom event bus in master improves test isolation, warns about publisher/subscriber loops and transaction/async ordering issues, and reports success integrating analytics with Segment.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:25About Chris
- 1:42Agenda
- 2:23Separation of Concerns
- 4:37Why is this important
- 5:59The importance of separation
- 7:52Overriding core functionality
- 9:07Publishing and subscribing
- 10:35Benefits
- 11:45Solidus Events
- 12:28Solidus Event Subscriber
- 13:56Adding Custom Events
- 15:44Testing
- 17:10Subscribe to Custom Event
- 17:35Unit Tests
- 22:42Resources
related talks
32mMake an Event of It
24mSolidus Internals, an adventure through less known features
42mIntroducing Event Sourcing into the Monolith: A Travelogue
36m"Business Logic in Ruby"
37mBuilt to last: A domain-driven approach to beautiful systems
35mModularizing Rails Monoliths One Bite at a Time
34mDon't Settle for Poor Names (or for Poor Design)
01h 47mWorkshop - Applications First, Frameworks Second: Better Systems through Design