EventDriven

Components communicate by emitting/reacting to events rather than direct calls — enables loose coupling and async workflows.

Why we need this / what value this brings

Decouples producers from consumers — a service doesn't need to know who's listening, enabling independent evolution and easy addition of new consumers.

When to use this

When multiple parts of the system need to react to the same state change (a booking being confirmed triggers email, SMS, and analytics).

How to use or implement this

Model key state transitions as events (BookingCreated, BookingConfirmed), publish them to a queue/bus, and let each interested consumer subscribe independently.

Research questions

• Where would event-driven fit Localz: booking state changes (created/confirmed/completed/cancelled) as the backbone?

---

Empty folder — drop notes, links, and findings here as you research.