EventDrivenIntegration
Integrating systems via events rather than direct calls — decoupling producers and consumers across system boundaries.
Why we need this / what value this brings
Decouples Localz from a partner's uptime/latency — an event queued now can be processed once the partner recovers, instead of the user-facing request failing.
When to use this
When the integration doesn't need an immediate synchronous response (e.g. sending a booking confirmation to a partner system).
How to use or implement this
Emit an event to a queue on the trigger action, have a separate worker process it against the third party with its own retry logic.
Research questions
- When is a webhook-out + queue-in pattern better than a synchronous API call to a partner?
Empty folder — drop notes, links, and findings here as you research.