Event Driven Architecture (EDA)
Managing Business Dynamics
for an Adaptive Enterprise
Dassana Wijesekara
Solutions Architect
dassana@wso2.com | stuka.wordpress.com }
Agenda
• Business Dynamics
• Definition of Event Driven Architecture (EDA)
• Characteristics of EDA
• Activities of an Event Driven System
• Main Components of Event Driven Architecture
• Event and Event Definition
• Event Channel : Queue / PubSub (Publisher/Subscriber)
• Model for Event Processing
• The Implementation Components
• EDA L0 & L1
• EDA Use Case : IoT & Cognitive Computing
• Summary
Business Dynamics
Business Pressure
Increased
Competition
Management
Strategies
System
Requirements
Architecture Style
Globalization
Personalized
Experience
Customer
Self Care
Regulatory
Pressure
Real-time
Enterprise
Predictive
Enterprise
Agile
Enterprise
Adaptive
Enterprise
Connected
Enterprise
Loose
coupling
Analytics
Scalability
Event
Processing
Event Driven Architecture (EDA)
• Event-driven architecture (EDA, also known as
Message-driven architecture) is a software
architecture pattern promoting the production,
detection, consumption of, and reaction to events.
An event can be defined as "a significant change
in state". (Wikipedia)
Characteristics of Event Driven Architecture
• Broadcast communication (+ point to point)
• Timeliness
• Asynchronous
• Fine grained events
• Ontology
• Complex event processing
Activities of an Event Driven System
Main Components of Event Driven Architecture
Event and Event Definition
Event Channel (Message Queue)
Event Channel (Pub Sub)
Event Processing Model
Event Processing Agent
The Implementation Components
The EDA L0
The EDA L1
WSO2 Advantage ?
Use Case : IoT & Cognitive Computing
Summary
• In order to adapt to business pressures IT systems should be agile, adaptive
and responsive.
• Event Driven Architecture is a architecture style which can support above
needs composed of events, event channels and event processing paradigms.
• Event channel is composed of messaging infrastructure and messaging
protocols. Message queues and pub sub are popular concepts and we see
hybrid models of those.
• Event processing provide the business value and performed through EPA
which may be on a distributed setup.
• WSO2 provide value at every corner on EDA space through its product
portfolio.
• IoT and Cognitive Computing is good use case for EDA.
Thank You!

Event Driven Architecture : Managing Business Dynamics for Adaptive Enterprise

  • 1.
    Event Driven Architecture(EDA) Managing Business Dynamics for an Adaptive Enterprise Dassana Wijesekara Solutions Architect dassana@wso2.com | stuka.wordpress.com }
  • 2.
    Agenda • Business Dynamics •Definition of Event Driven Architecture (EDA) • Characteristics of EDA • Activities of an Event Driven System • Main Components of Event Driven Architecture • Event and Event Definition • Event Channel : Queue / PubSub (Publisher/Subscriber) • Model for Event Processing • The Implementation Components • EDA L0 & L1 • EDA Use Case : IoT & Cognitive Computing • Summary
  • 3.
    Business Dynamics Business Pressure Increased Competition Management Strategies System Requirements ArchitectureStyle Globalization Personalized Experience Customer Self Care Regulatory Pressure Real-time Enterprise Predictive Enterprise Agile Enterprise Adaptive Enterprise Connected Enterprise Loose coupling Analytics Scalability Event Processing
  • 4.
    Event Driven Architecture(EDA) • Event-driven architecture (EDA, also known as Message-driven architecture) is a software architecture pattern promoting the production, detection, consumption of, and reaction to events. An event can be defined as "a significant change in state". (Wikipedia)
  • 5.
    Characteristics of EventDriven Architecture • Broadcast communication (+ point to point) • Timeliness • Asynchronous • Fine grained events • Ontology • Complex event processing
  • 6.
    Activities of anEvent Driven System
  • 7.
    Main Components ofEvent Driven Architecture
  • 8.
    Event and EventDefinition
  • 9.
  • 10.
  • 11.
  • 12.
  • 13.
  • 14.
  • 15.
  • 16.
  • 17.
    Use Case :IoT & Cognitive Computing
  • 18.
    Summary • In orderto adapt to business pressures IT systems should be agile, adaptive and responsive. • Event Driven Architecture is a architecture style which can support above needs composed of events, event channels and event processing paradigms. • Event channel is composed of messaging infrastructure and messaging protocols. Message queues and pub sub are popular concepts and we see hybrid models of those. • Event processing provide the business value and performed through EPA which may be on a distributed setup. • WSO2 provide value at every corner on EDA space through its product portfolio. • IoT and Cognitive Computing is good use case for EDA.
  • 19.