dotnetcore
feat: asb custom consumers
Description:
Current Situation: Currently, our Azure Service Bus provider lacks support for multiple namespaces and topics for consumers. We are utilizing a single topic within Azure Service Bus for messaging, and a single namespace for the application.
Solution Attempt: I have attempted to implement a solution that addresses this limitation, and it works as expected. However, I am currently unable to submit a pull request (PR) for this update.
Issue(s) addressed:
- https://github.com/dotnetcore/CAP/issues/1571
Changes:
add CustomConsumer topic
Affected components:
Azure service bus
How to test:
Provide a step-by-step guide on how to test your changes. Include any relevant information like environment setup, dependencies, etc.
Additional notes (optional):
Provide any additional notes or context that may be relevant to the changes.
Checklist:
- [ ] I have tested my changes locally
- [ ] I have added necessary documentation (if applicable)
- [ ] I have updated the relevant tests (if applicable)
- [ ] My changes follow the project's code style guidelines
Reviewers:
- Mention any reviewers you would like to review your PR. This can be helpful if you know someone who is familiar with the part of the codebase you're working on.
Hi @KuchaD. I will take a deeper look into this in the following days. Meanwhile, could you also update the documentation to include the custom consumers?
Have you guys considered just using message forwarding? https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-auto-forwarding
You can create a single topic for your service to consume and forward messages from other topics
@KuchaD @mviegas
