Event-Driven Integration

Publishing facts rather than commands, and versioning event schemas.

4Questions

11Flashcards

5Terms

Drill this topic All of API & Integration Architecture

Questions

4 to work through

advanced

An e-commerce platform integrates order, inventory, payment, logistics and notification through events. Which events should be commands and which should be notifications, and why does confusing them cause outages?

2 min answer
advanced

An event-collection platform routes customer telemetry to hundreds of downstream destinations with different reliability. What delivery guarantees are achievable, and how should destination failures be isolated?

2 min answer
advanced

An order service publishes events consumed by six teams. Every consumer immediately calls back for order details. What is wrong and what do you change?

2 min answer
advanced

You operate webhook delivery for 50000 integrators. One endpoint is down for two days. Design the delivery system.

2 min answer

Terminology

5 terms in this topic

concept

Command vs Notification

Whether a published message requests an action someone is responsible for, or states a fact the publisher does not care who consumes - and why confla…

pattern

Destination Isolation

Fanning events out by writing to a queue per destination rather than delivering synchronously to many, so that one failing or slow destination cannot…

concept

Event Notification vs Event-Carried State

Whether an event carries only the fact that something happened, or also the data a consumer needs to act on it.

practice

Event Versioning

Evolving event schemas without breaking consumers that may read messages written months earlier.

pattern

Event-Driven Integration

Integrating systems by delivering events rather than by polling or synchronous calls — including the delivery guarantees the receiver must be told about.

API & Integration Architecture