StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POAzure Mobile Services vs web sockets for device as a server
text
Body
copied!<p>I have in mind a scenario where a Windows 8 app will act as a server, receiving messages from diverse clients (other Windows 8 apps or Excel Web Apps). Those messages need to arrive at a low latency (<1s in most cases). I am considering many different solutions. I will definitely need some kind of server backbone to do the match making (route the messages to the appropriate device). And I try to decide between</p> <ol> <li><p>Azure Mobile Services. The source will send messages to Azure and Azure will send them as a push notification to the appropriate "server" device. The problem is that latency here is not very good.</p></li> <li><p>Azure Mobile Services (or something simpler like a simple Web API site) only for matchmaking: actual sending of messages would be established with each client having a web socket connection to the server app. Here we have very low latency, but I fear connectivity problems. The fact that the server won't store any messages is better from a data protection perspective, but makes disaster-recovery and handling moments where the server app will be on the background slightly more difficult.</p></li> <li><p>Azure Service Bus. It's supposed to be made for that (the server subscribes to the feed of client messages), but I think a new queue will need to be created for each server (and then clients will have to learn of the name of that queue, so some matchmaking like in option 2 will be necessary)</p></li> </ol> <p>What would you recommend?</p> <p>Thanks in advance!</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload