I need to design a communication platform for different services (part of the same application). They will need to exchange particular events in order to maintain consistency. Typically Service Bus Topics with multiple subscriptions are used for that purpose (one-to-many communication). However, it would make my life easier if all components used the same topic to publish events (many-to-many). Then subscriptions could filter out only those events that are important to them. So in the end this will decrease the amount of topics and subscriptions and would help me achieve a simpler design (instead of having one topic per publisher with multiple subscriptions; a single consumer might then have multiple subscriptions if it needs data from multiple publishers).
I have read all Service Bus constraints and limitations in the Microsoft documentation and was not able to find out if multiple components using a single topic is a good idea. Will I hit any limitations or encounter known problems? If two services (A and B) would publish events to that topic, will the order be maintained on the subscribing-side? As far as I understand, sessions are used per publisher, so perhaps this cannot be guaranteed.
I would appreciate if somebody could shed more light on this.