Event-Driven Architecture

Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Event-Driven Architecture

Source: ISO/IEC/IEEE 42010:2022

Source reference: https://www.iso.org/standard/74393.html

Additional information: Event-Driven Architecture (EDA) is a software architecture pattern that emphasizes the production, detection, consumption, and reaction to events that occur within a system. It is a distributed computing model that allows for the creation of loosely coupled systems, where components can communicate with each other without the need for direct integration. EDA is particularly useful in systems that require real-time processing and decision-making, such as financial trading systems, sensor networks, and IoT applications. The key benefits of EDA include scalability, flexibility, and agility, as well as the ability to respond quickly to changing business requirements.

Example: Event-Driven Architecture:
Decision: Implementing an event-driven architecture using Apache Kafka for asynchronous communication between microservices.
Rationale: Event-driven architectures enable loose coupling, scalability, and fault tolerance. Kafka provides a distributed messaging system with high throughput and fault-tolerant message persistence.

LOST view: Digital Solution Architecture Decisions Catalogue view

Identifier: http://data.europa.eu/dr8/egovera/Event-DrivenArchitectureGoal

EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal

ABB name: egovera:Event-DrivenArchitectureGoal

EIRA concept: eira:ArchitectureBuildingBlock

Last modification: 2023-06-15

dct:identifier: ADR-20230515180947546

dct:title: Architecture Decision Record about Event-Driven Architecture

eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.

eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.

eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]

eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.