search

dotnetcore / CAP

Distributed transaction solution in micro-service base on eventually consistency, also an eventbus with Outbox pattern
http://cap.dotnetcore.xyz
MIT License
6.61k stars 1.28k forks source link

Feature Request: Per-Queue Configuration for BasicQos and ConsumerThreadCount #1536

Closed ajdwfnhaps closed 2 months ago

ajdwfnhaps commented 3 months ago

Description Currently, it seems that RabbitMQ's BasicQos and ConsumerThreadCount parameters can only be configured globally across the entire service in CAP. It would be highly beneficial to have the ability to configure these parameters individually for each queue. This would allow for more granular control over the message processing behavior, tailored to the specific needs of different queues.

Proposed Solution Introduce the capability to configure BasicQos and ConsumerThreadCount on a per-queue basis within CAP's configuration. This could be achieved by extending the current configuration options to accept settings for each queue.

Use Case In scenarios where different queues have different performance and concurrency requirements, being able to specify `BasicQos

yang-xiaodong commented 3 months ago

We plan to support consumer concurrent in v8.2.0, please check out the PR https://github.com/dotnetcore/CAP/pull/1537 !

yang-xiaodong commented 3 months ago

@ajdwfnhaps Version 8.2.0-preview-233720681 is released, take a try.

ajdwfnhaps commented 3 months ago

got it, Thanks