Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce priorities for subscribers #50

Open
jollopre opened this issue Oct 13, 2024 · 0 comments
Open

Introduce priorities for subscribers #50

jollopre opened this issue Oct 13, 2024 · 0 comments

Comments

@jollopre
Copy link
Owner

jollopre commented Oct 13, 2024

A subscriber, also known as consumer, receives messages from the queue is subscribed to. Since a harmoniser process can have many subscribers running simultaneously, it might be interested to priority the delivery of messages to the subscribers. More info about this feature can be found here.

The prioritisation of higher consumers only takes place if the number of acknowledged messages is lower that the prefetch configured. That means subscribers not only have to be configured with manual ack but also have to set a prefetch count.

Although this feature can work independently of the concurrency option available for harmoniser, we believe is more suited for bounded concurrency configured so that under a process that already shared a number of threads, some subscribers are more prioritised than others.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant