Event Driven Architecture : Managing Business Dynamics for Adaptive Enterprise
Download as PPTX, PDF0 likes205 views
Event Driven Architecture (EDA) is a software architecture pattern that promotes the production, detection, and consumption of events to support agile and adaptive IT systems. Key components include event channels like message queues and pub/sub models, enabling real-time processing and business value generation. WSO2 offers solutions that enhance EDA capabilities, particularly for applications in IoT and cognitive computing.
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 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)
- 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!