Event-Driven Architecture

Normal Behavior

Decouples services by communicating state changes through asynchronous events.

Failure Behavior

Event schemas drift, consumers fail silently, and the system reaches an eventually inconsistent state forever.

Business Consequence

Event-driven architecture relies on producing, detecting, and consuming state changes (events) asynchronously. A systemic failure in the event broker leads to event loss, duplication, or severe backpressure. This breaks the fundamental data consistency across the enterprise, resulting in customers being charged without receiving digital goods or fulfillment systems acting on stale state, necessitating catastrophic manual database rollbacks.

Visual Manifestation

"A completely silent error landscape where all APIs return '202 Accepted', but downstream databases remain permanently empty because the events evaporated in transit."

Satirical Behavior

"A sophisticated architecture that replaces simple, synchronous error messages with asynchronous, untraceable silent failures."

Known Aliases

Technical Terminology

Failure Indicators