Designing a good routing topology for a highly-scalable system can be like mapping a graph. Many things need to be considered, for instance the problem, constraints of the environment, those of the messaging implementation, and performance strategies. What we often run up against is a lack of flexibility and expressivity in fitting routing to our needs. Here is where RabbitMQ stands out. api.agents.agent-{id}.operations.{operationName} In more complex cases the routing key may be combined with routing on message header fields and/or its content. An exchange examines a message's…