Question: Integration scenario with multiple queues about rqueue HOT 4 CLOSED

I was thinking about adopting the second option because if a problem occurs and maintenance is needed, this would not affect other functioning integrations.

This is 100% accurate and no one can deny this, but do we really need so many queues?

Two suggestion from my side

• Consider a prioritization approach. Perhaps creating five sub-queues, each independently handling its workload, could be a viable solution.
• Another strategy is to group low-throughput or similar sub integratrion messages into a single queue, simplifying the process of creating new queues.

It's crucial to assess the scale of your operations, including the volume of messages or events transmitted to each queue. Analyzing metrics such as averages, p95, and p99 can provide valuable insights.

Managing 575 queues might impose a significant burden on Redis, necessitating the addition of multiple Redis clusters to handle the resulting load.

It's important to recognize that there's no one-size-fits-all solution. Providing details such as message count, queries per second (QPS) at the queue or integration level, would aid in determining the optimal approach. Without a comprehensive evaluation of the options mentioned above, I would not recommend opting for 575 queues.

from rqueue.

I will try to study the integration process better and carry out some tests to define the best strategy.

Another question: I already have a redis instance configured in my springboot app, how can I specify another connection factory for Rqueue other than the one already used?

from rqueue.

That's good to know, please find the detail regarding new redis setup at https://sonus21.github.io/rqueue/configuration/redis-configuration/

from rqueue.

@joeldatabox I hope I've answered this question. Closing this for now. Please create or open a new ticket as you see.

from rqueue.