Scenario: During a usual business day, hundreds of thousands of customer transactions are running through an E2E Bridge process with steps like mapping, validation, transformation, backend notification etc.
Challenge: Some of the transactions have a higher priority than others and therefore need to be processed faster than other lower-priority ones.
Has anyone experienced a similar challenge? What was the solution?
What I could imagine, is to use a kind of prioritization service as a pre-processor: Collect all transactions into a kind of queue (DB?), including their corresponding priorities. Process entries in the queue timer-scheduled, always starting on top of the entries sorted by priority. Any practical experiences with something like this?
Unfortunately it’s not that easy – there aren’t high priority and low priority messages, but there is as stack of different priorities. The priority depends on the SLA defined with the specific customer and specific factors within the message payload.