Southbound Replies On REST

The order processing approach has been updated to ensure that all requests for a specific order are exclusively managed by the owner instance. This is accomplished by utilizing the JMS selector feature.

Despite the modifications, REST APIs remain accessible. After receiving an order event through REST, the Orchestrator initially fetches the instance ID of the order from the database. Then, it routes the request to EMS by appending the originator, orderID, and tenantID headers.

For every REST API, a corresponding EMS queue and set of listeners are established. When the owner instance receives a request on EMS, this request is then queued for further processing to the InternalOrderProcessor, also referred to as the worker thread.

This modification results in all communications via REST being asynchronous.