I am in the early stages of developing an Azure based application. One of the things that attracts me to Azure is scalability, given the variability in demand that I probably expect. As such, I try to keep things loosely coupled, so I can add examples when I need to.
The recommendations I saw for archiving an application for Azure include maintaining a minimal role for the web role and processing performed in worker roles, using queues for communication and some background storage like SQL Azure or Azure Tables. For me, this seems like a good idea, as I can scale one or both parts of the application without any problems. However, I am curious if there are any recommendations (or if anyone has experience) when it is best to just talk about the role of the web role directly in the data store or send data in turn?
I think of the case where I have a simple insertion that needs to be done from a web role - although I could set this as a message, send it to the queue and get the working role and execute Insert, it seems like a lot of double call. However, I am also grateful that in the end, it could be better if the web role is overloaded or more complex logic is needed for insertion.
I understand that this may be the case when the answer "is completely dependent on the situation, checks your Persian indicators" - but if someone has any thoughts, I would be very grateful!
thank
John
, - . , . ( ) ( ) -. - , . . , , , , , - . () .
, , , - , . , , Azure SDK, , . - Blade Azure Azure. , , , . . - -. , , , .
blob, , - , . , , , . , , .
:, , , , . , , "", . .
, , SignalR AJAX, , , .
, .
, -
, , , , .
, . , . , .
, , , , , Box Office, .
- , , Box Office. , , , , , , , . , .
:
, , , , ,
(Azure Amazon ) . Azure. : ( ) - ( ).