An event-driven architecture is a software architecture in which components communicate and initiate processing through events.
Event-driven architecture structures software around events and uses standardized event-driven patterns to increase functional and technical decoupling. section 13.3
La Redoute’s platform evolution
La Redoute used internal developer platform standards to move toward finer-grained modules aligned with business domains and functions. Its miniservices and standardized event-driven patterns reduced release and deployment dependencies while supporting scalable test environments and automated deployment-pipeline testing. section 13.3
How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it
How deep it goes
Connects standardized patterns to decoupling and modularity, but stops short of implementation details or pattern selection guidance.
Examples
Uses La Redoute’s domain-aligned miniservices, standardized event-driven patterns, scalable test environments, and automated deployment tests.
What you can do after
Evaluate event-driven patterns against organizational constraints such as company size, release dependencies, deployment dependencies, and testing needs.
How it connects
Connects event-driven architecture with internal developer platforms, miniservices, business domains, automated testing, and deployment pipelines.
Kafka for ArchitectsAn event-driven system is a software system whose components react to events rather than relying primarily on direct synchronous interactions.
Effective Platform EngineeringEvent architecture is a system design pattern in which components communicate and integrate through emitted and consumed events.
MongoDB 8.0 in Action, Third EditionAn event-driven application is an application whose components communicate and react through events rather than relying primarily on direct requests for data.
Learn Docker in a Month of Lunches, Second EditionAn event-driven architecture is a software design in which components publish events representing occurrences and other components react to those events.
Apache Kafka in ActionEvent-driven architecture is a software architecture in which components communicate by producing and consuming representations of events.
LatencyEvent-driven concurrency coordinates work by responding to events that signal changes or operation completions rather than blocking execution while waiting.
design patternkind of · A design pattern is a reusable, general solution structure for a recurring software design problem in a particular context.
eventuses · An event is an occurrence, change, or associated record or notification recognized as significant within a system or context.
Apache Kafkauses · Apache Kafka is a distributed event-streaming platform for publishing, storing, processing, and consuming streams of records.
asynchronous programminguses · Asynchronous programming is an execution approach in which operations can progress independently without requiring the initiating flow to wait for their completion or an immediate response.
message brokeruses · A message broker is intermediary software that receives, routes, and delivers messages between communicating producers and consumers.
request-response APIcontrasts with · A request-response API is an interaction pattern in which a requester sends a request to a provider and receives a corresponding response.
This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.
