Extending Solidus With the New Event Bus
summary
A revamped Event Bus exposes synchronous freeform events that are not persisted and carry arbitrary payloads; subscribers are modules placed under app/subscribers and must be registered at startup (use register events in pre-initializer). Testing offers scoped helpers like performing_only test helper and performing_nothing to silence listeners. Observability returns a firing object with execution times, caller location and listener results. The old adapter is deprecated and slated for removal in Solidus 4.0.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:25About Marc
- 0:51Trivia
- 4:18Agenda
- 4:44Extending Solidus
- 8:21Event Notification
- 12:48Domain Driven Design
- 14:37Subscriber Design
- 16:37Event Bus Interface
- 17:13Subscriber Module
- 18:44Registration
- 19:27Event Driven Behavior
- 20:37Event Helpers
- 21:11Observability
- 21:37Firing
- 22:02Conclusion
related talks
24mSolidus Internals, an adventure through less known features
02mSolidus Conf 2019 Recap Video
32mMake an Event of It
42mIntroducing Event Sourcing into the Monolith: A Travelogue
33mOpen Sourcing: Real Talk
22mBryan's ActieModel Extravaganza
35mDigging Deep with ActiveSupport::Notifications
52mUse the Source, Luke: High-fidelity history with event-sourced data