Service oriented architecture (SOA) provides a platform for IT environments that are more agile by enabling IT professionals to design flexible system that can adapt rapidly to meet the changing business needs of an enterprise. SOA implements a synchronous request-response model to connect remote processes in distributed system. It creates an inherent rigidity and additional dependencies when applied in modelling business processes and workflows. In contrast, event driven architecture (EDA) is based on an asynchronous message-driven communication model to propagate information throughout an enterprise. By describing business activities as a series of events it doesn’t bind functionally disparate systems and teams into the same management model. This allows it to support a more natural alignment with an enterprise’s operational model and processes/workflows. This session starts by analyzing key businesses challenges that encourage the use of EDA. Then we will deep dive into the fundamental concepts of EDA. Finally, we will discuss a pragmatic approach of designing and implementing an EDA using the WSO2 integration framework.

1. Event Driven Architecture (EDA)
Managing Business Dynamics
for an Adap5ve 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. Characteris5cs of Event Driven Architecture
• Broadcast communication (+ point to point)
• Timeliness
• Asynchronous
• Fine grained events
• Ontology
• Complex event processing

6. Ac5vi5es of an Event Driven System

7. Main Components of Event Driven Architecture

8. Event and Event Defini5on

9. Event Channel (Message Queue)

10. Event Channel (Pub Sub)

11. Event Processing Model

12. Event Processing Agent

13. The Implementa5on Components

14. The EDA L0

15. The EDA L1

16. WSO2 Advantage ?

17. UseCase :
IoT
Cogni5ve
Compu5ng

18. Summary
• In order to adapt to business pressures IT systems should be agile, adap5ve
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
porSolio.
• IoT and Cogni5ve Compu5ng is good use case for EDA.

19. Thank You!