Event mesh design

[mbeljic]

Hi,
We are designing system to asynchronously handle traffic form multiple data centers where each data center can have several hostnames/servers. We currently have one API application that would consume the data from all of the data centers. Now, the first option is to design the queue for each data center and subscribe corresponding topic to each queue. So, if we have for example three data centers (in reality tens of them) HEC45, HEC44, HEC55 then we would have for example queue with this name Queue_HEC45 and topic name hec45 and so on. In this case the application would be subscribed and received on push notification the data from all of the data centers. 

What would be recommended approach to design such system? 
What do you think in terms of pursuing SAP Advanced Event Mesh (Solace) instead of SAP Event Mesh? 
We definitely need guaranteed delivery, dynamic message routing in case of more consumer applications.

Thanks!

[fjaviergar07 · Accepted solution]

Hello,

You could have one queue for each of your Applications, which will be subscribed to the topics they are interested. For example, if the topic is: businessobject/<datacenter>

• And your app is is interested in the information coming from all datacenters you can subscribe to: businessobject/*
• If another app is interested in only the ones starting with HEC4 then you can subsrcibe to: businessobject/HEC4+
• If another app is only interested in HEC45, you can subscribe to: businessobject/HEC45

This you can achieve with Event Mesh in Integration Suite, but of course, Advance Event Mesh will give you much more options. For example, you could have one broker in each datacenter and build a mesh of brokers.

Best regards

Javier

[mbeljic]

Thank you Javier for your response!