Event Driven Architecture (EDA) is a software architecture pattern that promotes the production, detection, consumption of and reaction to events. EDA is composed of events, event channels like message queues and pub/sub, and event processing paradigms. It supports agile, adaptive and responsive systems by broadcasting and asynchronously processing events. EDA can help IT systems adapt to increased business pressures and dynamics through loose coupling, timeliness, scalability and real-time event processing. Example use cases include the Internet of Things and cognitive computing applications.

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
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

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 Event Driven Architecture
• Broadcast communication (+ point to point)
• Timeliness
• Asynchronous
• Fine grained events
• Ontology
• Complex event processing

6. Activities of an Event Driven System

7. Main Components of Event Driven Architecture

8. Event and Event Definition

9. Event Channel (Message Queue)

10. Event Channel (Pub Sub)

11. Event Processing Model

12. Event Processing Agent

13. The Implementation Components

14. The EDA L0

15. The EDA L1

16. WSO2 Advantage ?

17. Use Case : IoT & Cognitive Computing

18. 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.

19. Thank You!