PubSub
One message fans out to many independent subscribers — vs point-to-point queues where one message goes to exactly one consumer.
Why we need this / what value this brings
One event can fan out to many independent, decoupled consumers without the publisher knowing or caring who's listening.
When to use this
When multiple, independent parts of the system need to react to the same event (booking confirmed → email + SMS + analytics, all independently).
How to use or implement this
Publish a well-defined event to a topic; each consumer subscribes independently and can be added/removed without touching the publisher.
Research questions
- Where would pub/sub fit: e.g. a 'booking confirmed' event notifying email, SMS, and analytics simultaneously?
Empty folder — drop notes, links, and findings here as you research.