I'm curious what it would take to build a durable client side message queue solution using Service Bus for Windows Server AND Service Bus Azure. At a high level, what I (think I) want is to use Service Bus for Windows Server to process and/or contain any
failed messages if ever connectivity is lost between my site and Azure (internet outage.) When connectivity is restored the Message Bus on Windows Server would offload it's collection to Azure for processing. (I have multiple sites connected to the Azure Message
Bus which is why I cannot simply use the OnPrem solution as a simple pure fail-over)
How would you guys implement this? I've seen the concept of Federated Messaging in other frameworks but it doesn't seem that Azure supports it. I've looked into using the Azure auto forwarding too, but it seems that, because my OnPrem and Azure Services Buses are on different namespaces, that would probably not work.
The last thing I can think of, which I'm about to try, is to hand code the agents that will perform the error checking, holding and messaging, but I wanted to see what the community had to say about this.
Thanks,
Dave