Hello,
I have microservices architecture and I have integrated the Azure service bus and is working fine for all microservices. I have the below configuration.
Microservice 1
"Azure": {
"ServiceBus": {
"Connections": {
"Default": {
"ConnectionString": "MyConnectionString"
}
}
},
"EventBus": {
"ConnectionName": "Default",
"SubscriberName": "MyProject_Subscriber",
"TopicName": "MyProject_TopicName"
}
},
and having the same configuration in all other microservices.
Now the problem is, when a new entity is inserted in microservice 1 then it published the event to all microservices, and also I have a common TopicName for all the microservices. I want to integrate the below kind of configuration.
Example:
Microservice 1: Insert EntityA publish event to TopicNameA: Subscriber-only Microservice 2 Microservice 1: Insert EntityB publish event to TopicNameB: Subscriber-only: Microservice 2 and Microservice 3 Microservice 1: Insert EntityC publish event to TopicNameC: Subscriber-only: Microservice 4 Microservice 2: Insert EntityD publish event to "TopicNameD: Subscriber-only: Microservice 1
Basically, I want multiple topic names and dependent subscribers only for each microservices based on published events.
- ABP Framework version: v5.0.0
- UI type: Angular
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): yes
- Exception message and stack trace:No Exception
- Steps to reproduce the issue:"
2 Answer(s)
-
0
If Azure service bus support publishing events topic by topic, we can make improvements about it.
-
0
Ok, I will apply topic rules based on publishing events. If you have any sample or article or topics rules, would be great for us.
