To view recording of this webinar please use below URL: http://wso2.com/library/webinars/2015/09/event-driven-architecture/ Enterprise systems today are moving towards being dynamic where change has become the norm rather than the exception. Such systems need to be loosely coupled, autonomous, versatile and adaptive. There arises the need to model such systems, and event driven architecture (EDA) is how such systems can be modelled and explained. This webinar will discuss The basics of EDA How it can benefit your enterprise How the WSO2 product stack complements this architectural pattern

1. September 2015
Event Driven Architecture
Shiroshica Kulatilake
Solutions Architect

2. Agenda
• What’s Event Driven Architecture ?
• Why Event Driven Architecture ?
• How Event Driven Architecture can be done in the
enterprise ?
• How WSO2 supports Event Driven Architecture

3. Event Driven Architecture

4. Scenario : Health Care System

5. Scenario : Health Care System

6. Typical happenings
• A new patient registration
• Patient data update
• Patient payment
• Start a laboratory test
• Availability of laboratory results for a patient
• Revocation of insurance policy
• Drug outage
• etc …

7. Generalized View

8. Event Driven Architecture

9. Main Components of EDA

10. Main Components
• Event - entity depicting something which happened
• Event generator - entity which creates and pushes the
event
• Event channel - medium where the event lies before
consumption
• Event consumer - entity which consumes the event from
the channel

11. Event
• An event is a piece of information that may be applicable to
one or more objects at a given time
• An event would be
- self contained
- unique
- time relevant
• An event will propose
- a problem
- an opportunity
- a threshold
- a deviation, to its consumer
• Resulting action due to the occurrence of an event could be
- invocation of a service
- triggering a business process
- publishing of another event

12. Event Generators, Consumers &
Channel
• Event Generators
- publish events in the form of messages
- have no idea who would consume the message
- have no idea about the consequence of the messages
generated
• Event Consumers
- subscribe to published events
- handles events in an asynchronous manner
- oblivious to other consumers
• Event Channel
- acts as the mediator
- handles subscriptions
- handles storage and delivery

13. What is Event Driven Architecture
• It’s a way of building solutions based on the generation,
reception, processing and sending of events
• Events flow between decoupled services and
components
- Generators and Consumers are oblivious to each other
• Used for building extensible complex distributed systems
which are governed by asynchronous events
- There is no command and control structure
- No request and response mechanisms

14. What EDP brings to an Architecture
• Event hierarchies and fine grainedness
• Self describing nature of the event payload
• No special packing for each receiver
• Multiple receivers for a single event
• Responsibility of handling state is with the consumer
• Anonymity when sending an event
• Real time sending of events
• Async nature of delivery
• Guaranteed delivery

15. What EDP removes from an
Architecture
• Co-ordination
• Pre-planned continuity
• Global context with the latest status
• These only work where
- the individual executions are fast
- Actions only happen in a pre-defined order which
does not change frequently
- There is a fixed number of parties involved which the
primary orchestrator knows of

16. EDA in the Enterprise

17. Non-EDA based Health Care
System

18. Non-EDA Enterprise Integration
• Collection of Loosely coupled modules
• Enterprise Service Bus to manage the various point to
point integrations
• Business Process Server to do process flows
• Application servers to host the various services
• Central process handling
- via ESB
- via the BPS

19. Zooming on the centralized core
Predictive
Behaviour
Linear
Process
Flow
Centralized
Control
Request
Response
Based
Loosely
Coupled

20. What would EDA bring in
• Looser coupled flows
• Messages are self contained and follow a hierarchy
which helps to subscribe at the correct level
• No time is lost between occurrence and sending of the
event
• Asynchronous nature of event delivery
• Guaranteed delivery makes things more reliable
• Multiple event and multiple event stream processing

21. Why should an enterprise use EDA
• Enhances the ability to easily plug in more modules as
either event generators or consumers
• Asynchronous nature brings in the ability to design
solutions at run time by getting rid of linear flows
• Brings in the ability for reactive behaviour which suits
situations which need quick reactions
• Can add in more dimensions like monitoring, event
processing for overall system health as well as for
functionality purposes
• Capability to replay events if needed to either simulate,
when state needs to be recreated etc.

22. EDA based Enterprise System
Service Bus
Message Broker
Mediation Bus
End Service
Business
Process
Service Bus
Application

23. Event Management

24. It’s not a silver bullet ...
• There will be less build-time validation
• EDA creates rapidly evolving solutions
- too rapid ?
- how to keep track of ?
- how to debug ?
• Need of additional tools to figure out how things work
- Visualization tools needed for debugging
- Simulation tools needed for testing

25. EDA with WSO2 products

26. Components in an EDA setting

27. Components in an EDA setting
• Message Broker
- supports the various event based messaging patterns
- Queues/ Topics etc for pub/sub and P2P
- supports reliable message delivery
• Mediation / Service Bus
- brings together the different parties
- generates new events when needed
- can interact with non event based systems
- for business agility event messages would go through ESBs
- when it enters the ESB then would go through EIPs
• Business Process server
- deal with business flows that are triggered when an event occurs
- graphical editor to create the process

28. Messaging with WSO2 ESB

29. Messaging with WSO2 ESB

30. Components in an EDA setting
• Data Services Server
- create a service abstraction which can be used for events which
need to interact with data
• Registry
- provides the configuration repository
• Identity and Access Manager
- Authentication, authorization and handling fine grained access
control

31. Components in an EDA setting
• Activity Monitor
- for monitoring of all activity that goes around
- end to end business message flow monitoring
- identifying, collecting and tracing business transactions
- deriving KPIs from these stats
- taking decisions on these
• Complex Event Processor
- for multiple event and multiple event stream processing
- to go through event sequences and then detecting special events
(threats, opportunities, action points)
- for creating events as results
- for creating alerts
- for pattern detection which could be used for other purposes

32. Integrating with WSO2 DAS

33. Integrating with WSO2 CEP

34. EDA Reference Architecture - L0

35. EDA Reference Architecture - L1

36. EDA in Action

37. EDA based Health Care Scenario

38. EDA for Health Care with WSO2

39. FAQs

40. FAQ
• Is EDA pushing away SOA ?
- No, it still supports loose couple of services but
promotes more run time application definition, with
asynchronous components which act in a reactive
manner - It complements SOA
• Is EDA different to MOM ?
- EDA uses Message Oriented Middleware
infrastructure as the foundation
• Where does EIP stand with EDA ?
- The Enterprise Integration Patterns is about patterns
to integrate enterprise systems. Messaging is one and
the concepts in messaging are used in EDA

41. EIP - Messaging Patterns

42. Connect the WorldConnect the World