This image represents a system architecture for handling pricing data. Consumers (SavePricing1, SavePricing2, SavePricing3) process pricing messages and store results in the Product Result DB. These messages are then aggregated by a timer-based Aggregator Service. If all messages are received before the timer ends, a “Pricing Completed Message” is sent to an API gateway, which then posts the data to a third-party application. If the timer expires with pending messages, the remaining ones are marked as failed. A state message is also sent to update the status database based on each chunk’s success or failure.
