I am studying the restructuring of the application that I am working on to find a way to cut costs and provide us with much more scalability. In fact, the application is currently hosted on Azure as one large web application that users can log into, do some expensive computational work with the data stored in memory in the web application, and then ultimately exit system.
When looking at another way of scaling, one idea was to use working roles. Instead of processing a web application that currently requires us to use a rather expensive price level, we could use a service bus to send messages with the corresponding data to an instance of a working role that would perform this processing and send the results.
The most cost-effective way to do this, it seems, is to create a small instance of the working role for each user who logs in, who will deal exclusively with their requests (using, for example, a queue named after the user ID) and then be destroyed when the session ends user.
I have code to determine when to deploy an instance, how to pass these messages back and forth, and when to close an instance, but I find it difficult to find documentation for any methods or API calls that would allow me to do this easily. The closest I can find to delete the instance is described here , but I cannot find anything to create them.
What is the best way to deploy instances up and down Azure? What alternatives are available to me? I am also pleased to hear alternative suggestions on how to do this.
source
share