I have never used windows azure before, but this sounds like what you
are describing, communication between two roles of the same application.
http://blogs.msdn.com/b/avkashchauhan/archive/2011/10/30/communication-between-windows-azure-roles.aspx
"Only role instances that are part of the same Windows Azure application
can communicate with each other and this communication could occur only
over ports declared as internal endpoints within your Windows Azure
Application."
On 5/2/2012 7:20 PM, Rafel wrote:
Hello Glenn,
Thanks for the clean description and i understand what you say. Both
roles has their own kind of application where they are implemented.
But i am creating a website in which i want Grid View, Email Service
at some pages and some other parts that are in WebRole, also i have
another node chat application which is implemented in Worker Role. Now
i want to create a complete website which has Grid View, Email Service
and Chat functionality so for this i have to merger Web Role and
Worker Role, I am trying that but it give me error always.
Appreciate your help!!
Thanks.
On Apr 26, 8:37 pm, Glenn Block<[email protected]> wrote:
Hi Rafel
I work on the node/azureteam at Microsoft. Whether or not to create
many roles depends on what you are doing. The main benefit of WebRole
is IIS manages your node processes for you. It will spin up multiple
instances. It will monitor memory pressure and kill frozen instances
and restart them. We also provide access to logs over an http endpoint.
Further you can enable node-inspector for server side debugging withinAzurevia
our IIS integration.
The big benefit for worker is that it is leaner and it supports
WebSockets. In worker IIS is not present. This means there is less in
the box from a management perspective, but you get closer to the metal.
Because they are lighter they are more ideal for background processes
or for serving web apis.
One place where you might do a hybrid is for Websockets. For example
your front end might run in a WebRole with multiple instances while
your backend exposes web apis / uses WebSockets via a Worker.
Another scenario where you might use worker is for hosting an app
server like Redis / Mongo which your web role uses.
That being said, many folks just use one role and you do not have to
use multiple.
Hope this helps.
Sent from my Windows Phone
From: Rafel
Sent: 4/26/2012 8:51 AM
To: nodejs
Subject: [nodejs] Multiple Web Roles onAzure
Hello All,
I am a newbie to node. right now i am trying to create a web app using
node and deploying it onAzure. My idea is to create a website which
has simple tabs on menu bar and each tab open a new functionality e.g.
one tab gives me grid view, other give me email functionality, other
is for chat etc.
So my question is do i need to create multiple web roles in this case,
or combination of web roles and worker roles. How it goes?? give me an
idea.
I appreciate any help.
Thanks.
--
Job Board:http://jobs.nodejs.org/
Posting
guidelines:https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group
athttp://groups.google.com/group/nodejs?hl=en?hl=en
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
