azure - how to keep httprequest in sequence using multiple instances of web role -


We have a public FTP API and have just started to move it to esor. Architecture now using command pattern : The web API captures the HTTP request in a message queue, and then handles another app message. The most important thing is that http requests should be handled in the order of submissions. My questions are how to take advantage of scalability in Azure if I use a Web Roll hosted on Web API and turn on many instances of web role for high performance, how can I ensure that Many examples will put the request in queue storage (or service bus or table storage) order of their presentation?

If you do not currently have a custom sync mechanism, then this should not be any difference The API is running in an example or many. The only thing you need to do is to use the line of service bus which ensures brokerage messages. In this case the first message handlers coming in the queue will be the first, and so on.

If you are thinking of using some sync mechanism for http requests in the REST API, then you will lose scalability and performance, as all requests will be synchronous, and on how many role cases you have No matter, only one request is processed at one time. Hope it gives you some food for ideas.

Comments

Popular posts from this blog

c# - Textbox not clickable but editable -

Matlab transpose a table vector -

ios - Adding an SKSpriteNode to SKScene from a child SKSpriteNode -