azure - Using ASP.NET Web application as SignalR client -
my team in middle of deciding architecture of our backend system:
- webserver asp.net mvc application asp.net web api component, hosted in azure website.
- windows service b self-hosted owin server periodically push notifications clients subscribes notification, hosted in azure vm.
- windows service c client subscribes notification b, hosted in azure vm.
since more-or-less entrenched in .net
stack, implemented b signalr
server c being signalr
client. part seems work well.
now comes point want subscribe b, realize means asp.net web server going act signalr
client, instead of typical scenario acts signalr
server.
i presume can initialize signalr
connection in global.asax
, make process ever-running avoid appdomain
recycle. however, feel bit iffy when web server made other serving web requests. solution make web server not stateless since needs maintain web socket connection alive.
is there fundamentally wrong making asp.net
application signalr
client? there possible gotcha setup?
in azure cannot tell appdomain not recycle. because of many reasons, can restart heal , end making new connection singler server. ok you?
also singler used in web functionality improvement polling , refresh on web clients made simple. requirement seems end stuff, suggest go other event driven pattern. check azure service bus topic/subscription model have different components listen various events , act accordingly.
Comments
Post a Comment