Event driven Microservices Webinar
•Download as PPTX, PDF•
0 likes•89 views
Event-driven Microservices webinar presentation https://teams.microsoft.com/l/meetup-join/19%3ameeting_NzcyMWYxZGYtNGZjNi00ODdmLTg4ZmItNzE1ZWZiYzM4ZmJi%40thread.v2/0?context=%7b%22Tid%22%3a%224714a8d7-fffd-4c0f-9a98-8698ad2fd930%22%2c%22Oid%22%3a%2258829d4b-eab4-4d69-b572-1ef1c4b31808%22%2c%22IsBroadcastMeeting%22%3atrue%7d
Report
Share
More Related Content
Similar to Event driven Microservices Webinar
Similar to Event driven Microservices Webinar (20)
Recently uploaded
Recently uploaded (20)
Event driven Microservices Webinar
- 2. Microservices Enablement About Me Working at Sumerge for more than 3 years Senior Software Architect @amawaziny @amawaziny Ahmed El Mawaziny
- 3. Microservices Enablement Agenda 1.Recap on Intro Microservices Webinar 2.Microservices Challenges 3.Solutions with Event driven architecture
- 4. Microservices Enablement Recap on Intro Microservices Webinar
- 8. Microservices Enablement CoffeeShop Application Order Service Order Database Customer Service Customer Database
- 9. Microservices Enablement As a Coffee shop Manager, I want to add new drinks to application stock
- 10. Microservices Enablement CoffeeShop Application Order Service Order Database Customer Service Customer Database Stock Service Stock Database
- 11. Microservices Enablement As a Coffee shop Marketing Specialist, I want to send offers to customers via SMS
- 12. Microservices Enablement CoffeeShop Application Order Service Order Database Customer Service Customer Database Stock Service Stock Database Notification Service Notification Database
- 13. Microservices Enablement Microservices Challenges ● Adding new Microservice
- 14. Microservices Enablement How to manage transactions across Microservices? BEGIN TRAN T1; UPDATE ORDERS...; UPDATE STOCK...; SELECT * FROM CUSTOMERS; UPDATE ACCOUNTS...; COMMIT TRAN T1; New Order Order Database Stock Database Customer Database
- 15. Microservices Enablement Microservices Challenges ● Adding new Microservice ● Transaction across Microservices
- 16. Microservices Enablement How to build consolidated report in Microservices architecture? SELECT o.total as TotalOrder, c.NAME as CustomerName, s.ITEM_NAME as ItemName FROM ORDERS o JOIN STOCK s ON s.ITEM_ID = o.ITEM_ID JOIN CUSTOMERS c ON c.id = o.CUSTOMER_ID WHERE .... Report Order Database Stock Database Customer Database
- 17. Microservices Enablement Microservices Challenges ● Adding new Microservice ● Transaction across Microservices ● Reports
- 18. Microservices Enablement Solutions with Event-driven Architecture
- 19. Microservices Enablement What is Event-driven Architecture? “Event-driven architecture is a software architecture and model for application design. With an event-driven system, the capture, communication, processing, and persistence of events are the core structure of the solution. This differs from a traditional request-driven model.”
- 20. Microservices Enablement What is Events? • Publisher and Consumer subscription • Events are changes in the application state • Events in the past • Events cannot be changed • Events either async or sync
- 22. Microservices Enablement What is Event-Sourcing? “Event Sourcing ensures that all changes to application state are stored as a sequence of events. Not just can we query these events, we can also use the event log to reconstruct past states.” Martin Fowler
- 23. Microservices Enablement CoffeeShop Application with ES Order ServiceOrder Database Event Store Customer Service Customer Database Stock ServiceStock Database Notification Service Notification Database
- 24. Microservices Enablement Why to use Event-Sourcing? Temporal Query Complete Rebuild Data analytics Audit Event Replay
- 26. Microservices Enablement What is Saga? A saga is a sequence of local transactions. Each local transaction updates the database and publishes a message or event to trigger the next local transaction in the saga. If a local transaction fails because it violates a business rule, then the saga executes a series of compensating transactions that undo the changes that were made by the preceding local transactions
- 27. Microservices Enablement CoffeeShop Application with Saga Order ServiceOrder Database Event Store Customer Service Customer Database Stock ServiceStock Database ID CUST_ID TOTAL PENDING 100 1000 200 1 ID CUST_ID ORD_ID RESERVED 100 1000 100 1 AMOUNT 200 ID ITEM_ID ORD_ID ON_HOLD 100 10 100 1
- 28. Microservices Enablement CoffeeShop Application with Saga Order ServiceOrder Database Event Store Customer Service Customer Database Stock ServiceStock Database ID CUST_ID TOTAL PENDING 100 1000 200 0 ID CUST_ID ORD_ID RESERVED 100 1000 100 0 AMOUNT 200 ID ITEM_ID ORD_ID ON_HOLD 100 10 100 0
- 30. Microservices Enablement What is CQRS? CQRS stands for Command Query Responsibility Segregation. CQRS separates reads and writes into different models, using commands to update data, and queries to read data.
- 31. Microservices Enablement CoffeeShop Application with CQRS Order ServiceOrder Database Event Store Customer Service Customer Database Stock ServiceStock Database Reporting Service ElasticSearch/ NoSQL Database Notification Service Notification Database
- 32. Microservices Enablement Summary ● Microservices Benefits ● Microservices Challenges ● Event-Sourcing Pattern ● Saga Pattern ● CQRS
- 33. Microservices Enablement Resources ● https://martinfowler.com/eaaDev/EventSourcing.html ● https://microservices.io/patterns/data/saga.html ● https://microservices.io/patterns/data/cqrs.html
Editor's Notes
- Focus on Microservices Patterns
- Re-play all events to get application state
- Login and then faild is two events Order and CreditReserved then fails is OrderCread then CreditReserved then OrderFaild then CreditBack then OrderMarkedAsFaild Order from AWS is not guarantee that this item is available after submit Swing actionPerformed,mouseClicked, KeyPressed
- Re-play all events to get application state
- Complete Rebuild: We can discard the application state completely and rebuild it by re-running the events from the event log on an empty application. Temporal Query: with a blank state and rerunning the events up to a particular time or event. We can take this further by considering multiple time-lines Event Replay: If we find a past event was incorrect, we can compute the consequences by reversing, Production Issues replay on test server start new service and collect events then get application state
- One operation to be atomic transaction
- One operation to be atomic transaction
- Commands are void methods not returning anything Query is the read side