Scribd
Upload
58 views12 pages

Itelec 4

Uploaded by

adeyantigo05
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
58 views12 pages

Itelec 4

Uploaded by

adeyantigo05
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12

Group 2

Let’s Start
“ Principle and Benefits of
Event-Driven Architecture “
“

Event-driven architecture (EDA) is a


software design pattern where the
production, detection, consumption,
and reaction to events are the
primary focus of the architecture.
KEY COMPONENTS OF EVENT-DRIVEN ARCHITECTURE

Events: Messages or signals representing significant occurrences


or changes in a system.

Event Producers: Components or systems responsible for


generating events based on specific actions or triggers.

Event Consumers: Components or systems that receive and


process events, reacting to them by performing actions or
triggering workflows.

Event Bus/Broker: A messaging system that facilitates the


communication of events between producers and consumers,
ensuring events are routed to the appropriate recipients.

Asynchronous Processing: Events are processed independently


and asynchronously, allowing systems to react in real-time without
blocking or waiting for each other.
These components work
together to create a flexible,
scalable, and responsive
architecture where systems
can communicate and react to
events in a decoupled
manner.
Principle and benefits of event-driven architecture “

PRINCIPLES

Loose Coupling: Components within Scalability: Event-driven architecture


the system are loosely coupled, supports scalability by allowing
meaning they are independent and components to react to events
don't rely heavily on each other's state independently. This enables horizontal
or implementation details. This allows scaling by adding more instances of
for easier scalability and maintenance. event consumers as needed.
Flexibility and Adaptability: Systems built
Asynchronous Processing: Events
with event-driven architecture are more
are processed asynchronously,
flexible and adaptable to change. New
meaning the sender of an event
functionalities can be added by introducing
doesn't wait for the recipient to handle
new event types or modifying existing ones
it immediately. This asynchronous
without significant impact on the overall
nature enables better responsiveness
system.
and scalability.
Principle and benefits of event-driven architecture “

PRINCIPLES

Resilience: Since components are


Event-Driven Workflow: Systems
decoupled, failures in one component
follow a workflow based on event
don't necessarily affect the entire
occurrences rather than predefined
system. Fault isolation and resilience
sequences of actions. This allows for
are inherent in event-driven systems,
more dynamic and responsive
as failures can be contained within the
behavior.
affected components.
Principle and benefits of event-driven architecture “

BENEFITS

Real-Time Processing: Event-driven Fault Tolerance: Decoupling and resilience


architecture enables real-time features inherent in event-driven architecture
processing of events, allowing contribute to better fault tolerance. Systems can
systems to react to changes as they continue to function even if certain components
occur, leading to faster response fail, as long as alternative paths for event
times and better user experiences. processing are available.

Scalability and Performance: By Flexibility and Extensibility: Event-driven


decoupling components and systems are inherently flexible and
processing events asynchronously, extensible, allowing for easier integration of
event-driven architecture supports new functionalities, changes, and updates
scalability and improved performance, without disrupting existing components.
especially in distributed and
microservices-based systems.
Principle and benefits of event-driven architecture “

BENEFITS

Event Sourcing and Auditing: Event-


driven architecture facilitates event
sourcing, where system state changes
are recorded as a series of events. This Improved Developer Productivity: Developers
enables auditing, debugging, and can focus on building and maintaining individual
reconstruction of system state at any components without needing to worry extensively
point in time. about how they interact with other components.
This can lead to improved productivity and faster
Decoupled Systems Integration: Event- development cycles.
driven architecture facilitates integration
between heterogeneous systems by
enabling them to communicate through a
common event bus or messaging system
without tight coupling.
Overall, Event-Driven Architecture
provides a flexible and scalable
approach to building distributed
systems that can adapt to changing
requirements and deliver real-time,
responsive behavior.
Thank You

You might also like