Overview of the Eventuate Tram Customers and Orders application
5 likes•1,824 views
The document outlines an example project by Chris Richardson showcasing two key microservices patterns: Sagas for handling distributed transactions and CQRS for managing queries across multiple services. It details the architecture and functionalities of various services, including customer and order management, using Spring Boot and the Eventuate Tram framework. The document highlights the implementation of commands and queries, and emphasizes event-driven interactions within the system.
Overview of the Eventuate Tram Customers and Orders application
- 1. @crichardson About the Eventuate Tram Customers and Orders example Chris Richardson Founder of Eventuate.io Founder of the original CloudFoundry.com Author of POJOs in Action @crichardson [email protected] http://microservices.io http://eventuate.io Copyright © 2020. Chris Richardson Consulting, Inc. All rights reserved
- 2. @crichardson About the example Demonstrates two key patterns: Sagas - implement transactions that span services, https:// microservices.io/patterns/data/saga.html CQRS - implement queries that retrieve data from multiple services, https://microservices.io/patterns/data/cqrs.html Built using Spring Boot, JPA and the Eventuate Tram framework https://github.com/eventuate-tram/eventuate-tram-examples-customers-and-orders/ Note: this presentation describes the development branch , which reorganized/renamed the service modules. These changes will soon be merged into master
- 3. @crichardson System operations CustomersAndOrdersApplication ≪commands≫ createCustomer(name, creditLimit) createOrder(customerId, orderTotal) cancelOrder(orderID) ≪queries≫ findOrder(orderId) findOrderHistory(customerId)
- 5. @crichardson Customer Service - canvas
- 6. @crichardson Customer Service - domain model
- 7. @crichardson Order Service - canvas
- 8. @crichardson Order Service - domain model
- 9. @crichardson Order History Service - canvas
- 10. @crichardson Technical architecture Service: REST endpoint Pub/sub events Relational database - MySQL database Message broker Eventuate CDC - implements the Transaction Outbox pattern
- 11. @crichardson
- 12. @crichardson Why all these events!?
- 13. @crichardson Using the Saga pattern Customer has a credit limit createOrder() Creates Order Reserves credit cancelOrder() Updates Order Releases credit Event-driven a.k.a Choreography-based sagas https://microservices.io/patterns/data/saga.html
- 14. Using the CQRS pattern findOrderHistory() Returns customers and their orders Order History Service uses events to maintain a replica in MongoDB https://microservices.io/patterns/data/cqrs.html
- 15. @crichardson Customer Service Customer Controller Message Producer createCustomer() Customer* Events Order Event Consumer Order* events Customer Database ≪entity≫ Customer Customer Repository ≪service≫ Customer Service Domain Event Publisher POST /customers
- 16. Customer Service - code customer-service-api- messaging - events published by the service customer-service-api-web - DTOs for REST resources customer-service - service implementation
- 17. @crichardson Order Service Order Controller Message Producer createOrder() cancelOrder() Order* Events Customer Event Consumer Customer* events Order Database ≪entity≫ Order Order Repository ≪service≫ Order Service Domain Event Publisher POST /customers
- 18. Order Service - code order-service-api- messaging - events published by the service order-service-api-web - DTOs for REST requests and responses order-service - service implementation
- 19. @crichardson Order History Service CustomerOrder HistoryController findOrderHistory() Order History Event Consumer Order* events Order History Databas CustomerView Repository ≪service≫Ord erHistory ViewService POST /customers Customer* events
- 20. Order History Service - code order-history-service-api- web - DTOs for REST requests and responses order-service - service implementation
- 21. @crichardson Using the Saga pattern https://microservices.io/patterns/data/saga.html
- 24. @crichardson Using the CQRS pattern https://microservices.io/patterns/data/cqrs.html