- ABP Framework version: v8.2.1
- UI Type: Angular
- Database System: PostgreSQL
- Tiered (for MVC) or Auth Server Separated (for Angular): yes
Hello, I was trying to follow the docs to integrate Azure Service Bus, and I was trying to create a topic per event (Eto), but I couldn't, and after reviewing the code, docs, etc.. I came to the conclusion that all messages are sent to a single topic with a single subscriber.
This post seems to confirm the same: https://abp.io/support/questions/7116/Distributed-Event-Bus-Azure-Integration-with-outbox-pattern
If this is the case, why isn't this behavior configurable by default? Like if I have a microservices architecture, and service 1 listens to message X, service 2 listens to message Y, etc...
All services will receive ALL messages, even if they aren't supposed to. The event handler won't get triggered, but the message is being received, since the topic and the subscription are shared for all messages, no? so message filtering is being done in the code itself?
This causes too much traffic for messages that shouldn't have been sent in the first place. Messages like entity updates?
Our use case gets even worse, because we wanted to integrate with another app which should receive very specific messages. Now it will receive any message that is fired on that topic and we'd have to filter it.
Please advise if I understood this correctly. Thanks.
1 Answer(s)
-
0
hi
The Azure Service Bus implementation in ABP is relatively simple.
All messages are received and sent through a channel(
same SubscriberName and TopicName).You can use Azure Service Bus API to implement your requirements.
Thanks.
