event-driven architecture

A design in which services communicate by publishing and reacting to events, instead of calling each other directly and waiting.

In more detail

It separates a quick acknowledgement to the caller from the work that follows, lets consumers scale and fail independently, and absorbs bursts. The costs are duplicates, ordering questions and harder end-to-end tracing.

Example

Kafka often serves as the shared event log.

Related terms

Taught in

References