System architecture showing API request flow to Product API Service, queues, and consumers with correlation IDs and vendor mappings.

The image illustrates a backend system architecture where an API request is handled by a Product API Service. This service uses an API Configuration DB to determine vendor mappings and generates correlation IDs for each message. It communicates with MPN modules (MPN1 to MPNn), which then pass messages into vendor-specific queues. These messages are consumed by different vendors (Vendor1, Vendor2, Vendor3), and the entire process is tracked using correlation IDs. A State Service communicates with the Status DB to store the result, failure status, and reasons, ensuring traceability and monitoring of each transaction.

Leave a Reply

Your email address will not be published. Required fields are marked *

×

Table Of Content