Download as PDF, PPTX
Uploaded byPaulo Victor Gomes
Essay about event driven architecture
The document discusses moving from a monolithic architecture to an event-driven architecture (EDA) for an e-commerce system. In a monolithic system, services are tightly coupled and do not scale well. EDA loosely couples services so that they communicate asynchronously through event messages. The document provides an example where creating a product in one service triggers a "Product Created" event, which is handled by a central message bus and notification service to update other services like search and catalog without direct communication between services. Benefits of EDA include failure isolation, easy addition of new services, and improved scalability.
More Related Content
Similar to Essay about event driven architecture
Essay about event driven architecture
- 1. Essay about Event-Driven Architecture PauloVictor Gomes @pvgomes Twitter @Pv_fusion CTO at Natue - www.natue.com.br Voucher: PHPEXPERIENCE2017
- 2. Case - E-Commerce Inthis essay we will use the e-commerce as an example Shop - Customer - Catalog - Cart - Checkout - CMS - WMS - Freight….
- 3.
- 4. Monolithic Customer Catalog Cart Checkout Shop Customer CartCatalog Catalog Cart CMS CMS Url manager / SEO Checkout Newsletter Newsletter Newsletter Freight Freight Freight FreightWMS Thisdoes not scale very well It is very difficult to make changes
- 5. Service Oriented Architecture(SOA) is the solution We can divide the problem domain into separate systems
- 6. Beginning SOA’s approach Customer Catalog Cart Checkout Shop Customer CartCatalog Catalog Cart CMS CMS Url manager/ SEO Checkout Newsletter Freight Freight Freight Freight WMS
- 7. Beginning SOA’s approach Customer Catalog Cart Checkout Shop Customer CartCatalog Catalog Cart CMS CMS Url manager/ SEO Checkout Newsletter Freight Freight Freight Freight WMS
- 8. Keep moving forwardSOA’s approach... Customer Catalog Cart Checkout Shop Customer CartCatalog Catalog Cart CMS Url manager / SEO Checkout Newsletter Freight Freight WMS
- 9. Keep moving forwardSOA’s approach... Catalog Cart Checkout Shop Customer CartCatalog Catalog Cart CMS Url manager / SEO Checkout Newsletter Freight WMS
- 10. Keep moving forwardSOA’s approach... Catalog Cart Shop Customer CartCatalog Catalog Cart CMS Url manager / SEO Checkout Newsletter Freight WMS
- 11. Sometimes it’s notjust create a service Checkout Shop checkout page Order management - Purchase Order - Order Acceptance - Order Processing - Stock availability - Sales Return
- 12. Keep moving forwardSOA’s approach... Catalog Cart Shop Customer CartCatalog Catalog Cart CMS Url manager / SEO Checkout Newsletter Freight WMS Checkout-SPA Order Management
- 13. Keep moving forwardSOA’s approach... Catalog Cart Shop Customer Cart Cart CMS Url manager / SEO Checkout Newsletter Freight WMS Checkout-SPA Order Management Search API
- 14. Bye Bye Monolithic Catalog Shop Customer Cart CMS Url manager/ SEO Newsletter Freight WMS Checkout-SPA Order Management Search API Stock API
- 15. Bye Bye Monolithic Catalog Shop Customer Cart CMS Url manager/ SEO Newsletter Freight WMS Checkout-SPA Order Management Search API Stock API
- 16. Bye Bye Monolithic Catalog Shop Customer Cart CMS Url manager/ SEO Newsletter Freight WMS Checkout-SPA Order Management Search API Stock API A lot of point to point integration
- 17. Introduction of Event-DrivenArchitecture (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" K. Mani Chandy Event-Driven Applications We make a change to the state of a system, we record that state change as an event, and we can confidently rebuild the system state by reprocessing the events at any time in the future... Martin Fowler
- 18.
- 19. EDA Main Goal EDAis not just about agnostic services, is more about reacting through the Events
- 20. EDA - Eventreactions Product flow example
- 21. BackOffice EDA - Eventreactions Product flow example
- 22. BackOffice Catalog+POST +PUT +PATCH +DELETE Product EDA -Event reactions Product flow example
- 23. BackOffice Catalog+POST +PUT +PATCH +DELETE Product Search Product +POST +PUT +PATCH +DELETE EDA -Event reactions Product flow example
- 24. BackOffice Catalog+POST +PUT +PATCH +DELETE Product Search Product +POST +PUT +PATCH +DELETE Feed Product +POST +PUT +PATCH +DELETE EDA -Event reactions Product flow example
- 25. EDA - Eventreactions Product flow example BackOffice Catalog+POST +PUT +PATCH +DELETE Product Search Product +POST +PUT +PATCH +DELETE Feed Product +POST +PUT +PATCH +DELETE MarketPlace+POST +PUT +PATCH +DELETE Product
- 26. EDA - Eventreactions - Product flow example BackOffice Catalog+POST +PUT +PATCH +DELETE Product Search Product +POST +PUT +PATCH +DELETE Feed Product +POST +PUT +PATCH +DELETE MarketPlace+POST +PUT +PATCH +DELETE Product Catalog must know all services, e-commerce flow, it isn't agnostic A lot of point to point integration
- 27. EDA - Eventreactions - Product flow example BackOffice Catalog+POST +PUT +PATCH +DELETE Product Search Product +POST +PUT +PATCH +DELETE Feed Product +POST +PUT +PATCH +DELETE MarketPlace+POST +PUT +PATCH +DELETE Product Let's try another approach
- 28. EDA - Eventreactions Another approach BackOffice Catalog+POST +PUT +PATCH +DELETE Product Search Product Feed MarketPlace+GET Product +GET +GET Product
- 29. EDA - Eventreactions Another approach BackOffice Catalog+POST +PUT +PATCH +DELETE Product Search Product Feed MarketPlace+GET Product +GET +GET Product
- 30. EDA - Eventreactions - Product flow example BackOffice Catalog+POST +PUT +PATCH +DELETE Product Search Product +POST +PUT +PATCH +DELETE Feed Product +POST +PUT +PATCH +DELETE MarketPlace+POST +PUT +PATCH +DELETE Product
- 31. EDA - Eventreactions - Product flow example BackOffice Catalog+POST +PUT +PATCH +DELETE Product Search Product +POST +PUT +PATCH +DELETE Feed Product +POST +PUT +PATCH +DELETE MarketPlace+POST +PUT +PATCH +DELETE Product When will our services call Catalog?
- 32. EDA - Eventreactions Another approach BackOffice Catalog+POST +PUT +PATCH +DELETE Product Search Product Feed MarketPlace+GET Product +GET +GET Product
- 33. EDA - Eventreactions - Product flow example BackOffice Catalog+POST +PUT +PATCH +DELETE Product Search Product +POST +PUT +PATCH +DELETE Feed Product +POST +PUT +PATCH +DELETE MarketPlace+POST +PUT +PATCH +DELETE Product Perhaps a cronjob?
- 34. EDA - Eventreactions EDA approach BackOffice Catalog+POST +PUT +PATCH +DELETE Product Search Feed MarketPlace ?
- 35. EDA - Eventreactions EDA approach BackOffice Catalog+POST +PUT +PATCH +DELETE Product Search Feed MarketPlace Central Message Bus Product Created Product Updated Product Deleted
- 36. EDA - Eventreactions EDA approach BackOffice Catalog+POST +PUT +PATCH +DELETE Product Search Feed MarketPlace Central Message Bus Product Created Product Updated Product Deleted Events
- 37. EDA - Eventreactions EDA approach BackOffice Catalog+POST +PUT +PATCH +DELETE Product Search Feed MarketPlace Central Message Bus Product Created Product Updated Product Deleted Central Message Handler
- 38. EDA - Eventreactions EDA approach BackOffice Catalog+POST +PUT +PATCH +DELETE Product Search Feed MarketPlace Central Message Bus Product Created Product Updated Product Deleted Central Message Handler
- 39. EDA - Eventreactions EDA approach BackOffice Catalog +POST +PUT +PATCH +DELETE Search Feed MarketPlace Central Message Bus Central Message Handler MarketPlace Product Created
- 40. EDA - Eventreactions EDA approach BackOffice Catalog +POST +PUT +PATCH +DELETE Search Feed MarketPlace Central Message Bus Central Message Handler MarketPlace Product Created
- 41. The benefits - Iferror raises on service, the message remains in queue - It will be picked up later - Services don’t need to know about how to make updates to other services - Adding more services is easy - Scales well
- 42. References - Event DrivenArchitecture - K. Mani Chandy - What do you mean by “Event-Driven”? - Martin Fowler - Programming Without a Call Stack - Gregor Hohpe - Event Driven Architecture – The Basics - John Mathon
- 43. Thank you Twitter @Pv_Fusion Slack@pvgomes Github github.com/pvgomes pv.gomes89@gmail.com https://joind.in/talk/0525a