AWS Serverless and Microservices — Part 4

  1. Order_Initiated
  2. Payment_Success
  3. Payment_Failed
  4. Restaurant_Confirmed_Order
  5. Restaurant_Rejected_Order
  6. Delivery_Scheduled
  1. Payment Service shall be interested in Order_Initiated event. When initiated, it will initiate the Payment process.
  2. Restaurant Service shall be interested in Payment_Success event. On receiving the event, it will initiate the Order confirmation flow with Restaurant.
  3. Delivery Service shall be interested in Restaurant_Confirmed_Order event. Once the event is received, it will schedule delivery of the order.
  4. Payment Service shall be interested in Restaurant_Rejected_Order event. If the Order is rejected by the Restaurant because of whatever reason, Payment service needs to initiate the Payment Refund process.
  5. Order Service shall be interested in all the events. Reason is — it needs to update the status of the Order in its Database.
  6. Notification Service shall be interested in almost all the events as the service needs to inform the end user about every status change in the Order (Wow…Team is thinking about good User Experience 😏)
1) New Order Placement — Order_Initiated event emitted
2) New Order Placement — Payment_Success event emitted
3) New Order Placement — Restaurant_Confirmed_Order event emitted
4) New Order Placement — Delivery_Scheduled event emitted

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Naresh Waswani

Naresh Waswani

#AWS #CloudArchitect #CloudMigration #Microservices #Mobility #IoT