Event-Driven Architecture

Normal Behavior

A software architecture paradigm promoting the production, detection, consumption of, and reaction to events.

Failure Behavior

May drop requests or fallback to degraded mode under load.

Business Consequence

Event-Driven Architecture relies on asynchronous state changes to trigger distributed microservices. If the foundational event backbone fails or experiences severe lag, the entire microservice ecosystem becomes decoupled in time. Orders are placed but never processed, payments are captured but receipts are never sent, and inventory is not decremented. This systemic asynchronous failure creates massive data inconsistencies across domains, requiring weeks of manual data reconciliation.

Visual Manifestation

"Consumer lag metrics spike exponentially on Grafana dashboards; dead-letter queues overflow with poison pill messages, and user interfaces show perpetual loading spinners waiting for asynchronous callbacks that never arrive."

Satirical Behavior

"A complex mechanism for ensuring that when a system breaks, it breaks asynchronously, downstream, and in a way that requires consulting five different teams to figure out who dropped the JSON payload."

Known Aliases

Technical Terminology

Failure Indicators