Skip to content
This repository has been archived by the owner on Aug 31, 2021. It is now read-only.

Detect if a request cannot be routed and return immediately #43

Open
jpwilliams opened this issue Aug 10, 2017 · 2 comments · May be fixed by #101
Open

Detect if a request cannot be routed and return immediately #43

jpwilliams opened this issue Aug 10, 2017 · 2 comments · May be fixed by #101

Comments

@jpwilliams
Copy link
Owner

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.

@jacktuck
Copy link
Collaborator

Where's the performance hit?

@jpwilliams
Copy link
Owner Author

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Test Project
  
Open Issues
Development

Successfully merging a pull request may close this issue.

2 participants