StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12064144
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2012-08-21T22:48:43.620
FavoriteCount
0
LastActivityDate
2012-08-22T01:09:55.063
LastEditDate
2012-08-22T01:09:55.063
LastEditorUserId
728584
OwnerUserId
728584
ParentId
12063346
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
AS stated above, a little bit more context is needed. You basically have two main options, Windows Azure Queues and Windows Azure Service Bus Queues/Topics. My personal advice would be to use Azure Queues if the Web and Worker Roles are colocated in the same region and Service Bus Queues if they are not. I would have to ask why are you not colocating your Web and Worker Roles together, if you have a geographic deployment of you app then look at deploying all your Web Roles and Work Roles in each Region e.g. US, Europe & Asia and then use Traffic Manager to route user to the optimal region. There is a good blog post on when to use which queue 'Windows Azure Queues and Windows Azure Service Bus Queues - Compared and Contrasted': <a href="http://msdn.microsoft.com/en-us/library/windowsazure/hh767287.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/windowsazure/hh767287.aspx</a> HTH EDIT A good approach for Web and Worker Role communication is below (I stole this from a recent thread which @smarx answered) 1 Web role writes a message to the queue that includes a job ID. 2 Worker role does the work and writes the result to a table with partition key . 3 Web role is polling that row of the table. Once it exists, the answer comes back. In your case you could have the Worker Role update the Table Storage with the status updates and then have your Web Role pick them up and display them to the user. e.g. 20%, 50%, Complete etc... I don't really see delays in this type of communication, as long as you are polling sufficiently from the Web Role (*note transactions costs) I presume some sort of Inter Role communication could be done here for status updates but it might be overkill IMO: <a href="http://msdn.microsoft.com/en-us/library/windowsazure/hh180158.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/windowsazure/hh180158.aspx</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBest way to comunicate between ASP.NET app and Worker Role
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USuser728584
UserOwnerUserId
1. USuser728584
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POBest way to comunicate between ASP.NET app and Worker Role
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.