[WSO2Con Asia 2018] Building Reactive Applications Using Event-driven Architecture
1 like338 views
Event-driven architecture (EDA) is a software design pattern focusing on event production and consumption, allowing systems to react to changes in state. It promotes decoupling between event producers and consumers, enhancing system resilience and scalability, particularly in reactive applications. EDA can complement service-oriented architecture and is well-suited for serverless computing environments.
[WSO2Con Asia 2018] Building Reactive Applications Using Event-driven Architecture
- 1. Architect / Associate Director, WSO2 Building Reactive Applications using Event-driven Architecture Joseph Fonseka
- 2. Event-driven Architecture Event-driven architecture (EDA), is a software architecture pattern promoting the production, detection, consumption of, and reaction to events. - Wikipedia
- 3. What is an Event ? An event can be defined as "a significant change in state" - When a user clicks a button "button state changes" - When a consumer purchases a car, the car's state changes from "for sale" to "sold" In a system an Event can be represented with an Object or a message. When an event it occured it will get Notified to other subsystems.
- 4. This happens when a system sends event messages to notify other systems of a change in its domain. - Source system doesn't really care much about the response. - Event do not need to carry all the data, Receiver can send a request to the sender to retrieve more data if required. - Implies a low level of coupling, and is pretty simple to set up. Event Notification
- 5. Event Notification // Get the button, and when the user clicks on it, execute myFunction document.getElementById("myBtn").onclick = function() {myFunction()}; /* myFunction toggles between adding and removing the show class, which is used to hide and show the dropdown content */ function myFunction() { document.getElementById("myDropdown").classList.toggle("show"); } Commonly found in UI Frameworks
- 11. Pros : Receiver and Sender is decoupled. Cons: Overall behaviour of the system is not captured in the code. Event Notification
- 15. Pros : More decoupled. Reduced load on the sender More resiliency Cons: Replicated Data -> Eventual Consistency Complexity of Receiver Event-Carried State Transfer
- 16. What is a Reactive App?
- 17. Core building blocks of a Reactive Application Reactive Application Responsive Resilient Message Driven Scalable
- 18. How to Implement ?
- 19. <events><events> EDA High Level Event Channel System A System B System C System D <events><events> Event Producer Event Consumer
- 20. <events><events> EDA High Level Event Channel System A System B System C System D <events><events> Event Producer Event Consumer Analytics CEP Analytics CEP
- 21. <events><events> EDA Event Channel System A System B System C System D <events><events> Analytics CEP API Gateway Sample Text Analytics CEP
- 22. Do I have to re-write ?
- 23. EDA in Brownfield Projects Legacy Monolith Application Agent Event Channel System A System B System C System D
- 24. ● Event-driven architecture can complement service-oriented architecture (SOA) because services can be activated by triggers fired on incoming events. EDA + SOA
- 25. ● EDA is a good fit for Serverless Architecture. ● You can have function that written by developers run in stateless compute containers that are event-triggered. ● The functions may only last for one invocation and fully managed by a third party. Serverless with EDA
- 26. EDA is Architecture not a Solution.