Add queues per function

[bmcgoncalves]

Add this feature if its possible. We would like to add queues per function. Users using rabbitmq only need to know the name of the functions.

@RMQRoute({queue: '/cmd/sum', 'routingKey': '/cmd/sum', ...})
sum(numbers: number[]): number {
    return numbers.reduce((a, b) => a + b, 0);
}

@RMQRoute({queue: '/cmd/info', 'routingKey': '/cmd/info', ...})
info(data: string) {
    console.log(data);
}

`

Example:

[AlariCode]

@bmcgoncalves, thanks for suggestion! Can you describe use case when you need to listen to more than one queue? Why can't you subscribe to one queue and use Topic to route messages to functions? You can name queue like "myService.queue" and add routes:

• /cmd/sum
• /cmd/info

This adds more complexity to routing and managing queues. You need to keep in mind that your service consumes more than one queue.

[bmcgoncalves]

Hi,

Imagine if I have 1000 microservices connected to the same queue. I'm new to rabbitmq but I think this is not a good practice.

I want to create microservices in NestJs and make them"auto registered" in the rabbitmq to make my functions available to all others microservices. The developer making a a microservice only need to know the Routing-Key/queue (the same string) and call services by function name (Routing-Key).

[AlariCode]

Good practice in RMQ - you have 1 queue per service. So when you have 1000 different services you will have 1000 queues. But if you have same services (for load balancing) they will be connected to the same queue and process messages one by one. But if you have 1 service connected to multiple queues - this may cause queue management problem.