You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 31, 2021. It is now read-only.
If a request cannot be routed to a queue, it'd be nice to know as soon as possible.
We can use the mandatory message option to have the message returned if that's the case, meaning we can throw an error back to the user that no such endpoint exists.
This does, however, come with a performance hit; it may be pertinent to expose this functionality as an optional extra.
The text was updated successfully, but these errors were encountered:
RabbitMQ in the past has published benchmarks where publishing wit mandatory: true has severely impacted performance. There have been blogs/updates since which mention improvements to the speed, though it's my understanding that there's still a small performance hit when using that flag.
If a request cannot be routed to a queue, it'd be nice to know as soon as possible.
We can use the
mandatory
message option to have the message returned if that's the case, meaning we can throw an error back to the user that no such endpoint exists.This does, however, come with a performance hit; it may be pertinent to expose this functionality as an optional extra.
The text was updated successfully, but these errors were encountered: