Closed yijiyap closed 4 months ago
Note how there are 2 main flow of events concerning the match booking service:
The Match Booking Orchestrator Microservice is designed to perform the following actions in response to the user checking out in the Checkout UI:
Interact with the Match CRUD Service: Request ticket availability from Match CRUD Service Return ticket availability from Match CRUD Service
Send ticket information to the Seat Reservation UI
Send match information to the Ticket Reservation Service to lock seats.
Interact with billing service: Send the ticket information to the billing service for a purchase.
Interact with RabbitMQ Broker: Send all the match and ticket information to the message queue.
gg
yijiyap
commented
4 months ago
Note how there are 2 main flow of events concerning the match booking service:
The Match Booking Orchestrator Microservice is designed to perform the following actions in response to the user checking out in the Checkout UI:
Interact with the Match CRUD Service: Request ticket availability from Match CRUD Service Return ticket availability from Match CRUD Service
Send ticket information to the Seat Reservation UI
Send match information to the Ticket Reservation Service to lock seats.
Interact with billing service: Send the ticket information to the billing service for a purchase.
The Match Booking Orchestrator Microservice is designed to perform the following actions in response to the user checking out in the Checkout UI:
Interact with RabbitMQ Broker: Send all the match and ticket information to the message queue.