.net - Azure Mobile Services vs web sockets for device as a server -
i have in mind scenario windows 8 app act server, receiving messages diverse clients (other windows 8 apps or excel web apps). messages need arrive @ low latency (<1s in cases). considering many different solutions. need kind of server backbone match making (route messages appropriate device). , try decide between
azure mobile services. source send messages azure , azure send them push notification appropriate "server" device. problem latency here not good.
azure mobile services (or simpler simple web api site) matchmaking: actual sending of messages established each client having web socket connection server app. here have low latency, fear connectivity problems. fact server won't store messages better data protection perspective, makes disaster-recovery , handling moments server app on background more difficult.
azure service bus. it's supposed made (the server subscribes feed of client messages), think new queue need created each server (and clients have learn of name of queue, matchmaking in option 2 necessary)
what recommend?
thanks in advance!
i have been developing similar before, suggest build solution using windows azure mobile solutions supports node js npm right now.
for client suggest build using signalr designed cases such yours real time applications require lot of transactions server side.
you can find more details how can integrate both of them in following link: http://hhaggan.wordpress.com/2013/07/12/signalr-node-js/
i hope these you, let me know if need else.
Comments
Post a Comment