Splitting a single event queue into multiple publish queues

When you handle a high volume of event messages, processing them through a single event queue can quickly become a bottleneck. As the system scales and the number of messages increases, you may encounter the following issues:

• Performance degradation

• Delayed message processing

• Difficulty tracking and analyzing message flows

To address these issues and improve both processing efficiency and observability, you can introduce multiple publish queues, each dedicated to a specific entity or domain. This separation allows messages to be processed independently, reducing contention and improving throughput.

For instructions on setting up multiple queues, see Integrating multi-queue publish structure .