Tech USP: Realtime is default. Server-Sent Events (SSE) instead of WebSocket setup. Cross-aggregate updates via multi-stream projections.
Buyer’s view: Live updates like status pages, chats or dashboards work without a Pusher/Ably subscription. When someone changes a record, everyone else sees the change without reloading the page.
Highlights
- SSE endpoint built in:
/ssewith heartbeat (15s), Bun idle-timeout handling - Async broadcast: write handler emits an event, SSE consumer picks it up and broadcasts to connected clients
- Per-tenant separation: clients only see events from their own tenant
- Multi-stream projection: cross-aggregate read models (e.g. dashboard pulling events from 5 aggregates)
- Dead-letter queue: failed projections land in a dedicated table for ops
- Clean multi-instance: with multiple API instances, each client receives each event exactly once
Architecture deep dive
- event-dispatcher: async delivery, dead letter, retention
- projections: single-stream vs cross-aggregate
Continue in the docs