Emit Once, Notify Anywhere
summary
A typed domain event bus that starts from one emit and routes to a single emission point now drives 5 notification providers, 55 event types, and 4 compound notification flows while also handling analytics webhooks and audit logs for free. It uses TypeScript plus Zod for runtime validation and schema-parsed payloads, templates to format per-channel output, dependency injection for push email and preferences services, and enforces user notification preferences so channels stay consistent and spammable states are prevented.
AI-written summary · about
chapters (6)
- 0:00Introduction and motivation
- 2:50Notification complexity grows
- 7:21Designing the event system
- 10:55System architecture overview
- 13:49User preferences and safety
- 16:41How it all works together
related talks
34mBuilding a scalable multichannel notification system
53mMessaging: The fine line between awesome and awful
01h 31mTutorial: Zbus - the Lightweight & Flexible Zephyr Message Bus
18mThe only in-app notification library that you will ever need
09mCommunicating Between Components
01h 54mHow to design your messages: Patterns and tradeoffs in Event Driven Architectures Workshop
54mSo You Want to Build An Event Driven System?
15mA Reusable Zbus Based Architecture, Abstracting Core Application...