它是重用后端处理的Azure的Web角色是一个好主意？ [英] Is it a good idea to reuse an Azure web role for backend processing?

问题描述

我移植一个巨大的应用到Windows Azure。这将有一个网络服务前端和一个加工后端。到目前为止，我想我会使用网络角色服务的客户端请求和工人角色的后端处理。

I'm porting a huge application to Windows Azure. It will have a web service frontend and a processing backend. So far I thought I would use web roles for servicing client requests and worker roles for backend processing.

管理两个种角色似乎有问题 - 我需要决定如何标度的两个种角色，也是我需要每几个（至少两个）情况，以确保合理的容错性，这将略微增加运营成本。此外，在我的应用程序客户端的请求是相当轻巧，后端处理是重量级的，所以我预计，后端处理会消耗远远更多的处理能力比服务客户的请求。

Managing two kinds of roles seems problematic - I'll need to decide how to scale two kinds of roles and also I'll need several (at least two) instances of each to ensure reasonable fault tolerance and this will slightly increase operational costs. Also in my application client requests are rather lightweight and backend processing is heavyweight, so I'd expect that backend processing would consume far more processing power than servicing client requests.

这就是为什么我在考虑使用Web角色的一切 - 只是生成线程，做中的每个实例都请求提供服务和后端处理。这将使得角色更加复杂，但我会猜测简化管理。我将有一个统一的作用，更多的实例和更好的容错性。

This is why I'm thinking of using web roles for everything - just spawn threads and do both servicing requests and backend processing in each instance. This will make the role more complicated but will I guess simplify management. I'll have more instances of a uniform role and better fault tolerance.

这是个好主意，重复使用Web角色的后端处理？我应该期待什么缺点？

Is it a good idea to reuse web roles for backend processing? What drawbacks should I expect?

推荐答案

听起来像是你已经有什么想使用多个角色时约pretty好主意：

Sounds like you already have a pretty good idea of what to think about when using multiple roles:

• 成本两个实例，以满足SLA（虽然有些后台任务真的不需要SLA如果最终用户不会看到的影响）


• 单独的刻度单位

不过：如果你在一个角色上运行的一切，那么一切秤在一起。比如说，如果你有8000端口的管理网站，你可能很难达到它，如果你的用户群与交通一声主网站上的端口80。

However: If you run everything in one role, then everything scales together. If, say, you have an administrative web site on port 8000, you might have difficulty reaching it if your user base is slamming the main site on port 80 with traffic.

我的博客上讲述相结合的网络和辅助角色，的这里，它进入更详细一点沿着我们讨论这里。此外，由于三月份一段时间，每个角色5端点的限制被取消 - 见我的博客文章的这里多远，你现在可以推的端点。有了这个限制较少的终端模式真的打开了单一角色部署新的可能性。

I blogged about combining web and worker roles, here, which goes into a bit more detail along what we're discussing here. Also, as of some time in March, the restriction of 5 endpoints per role was lifted - see my blog post here for just how far you can push endpoints now. Having this less-restrictive endpoint model really opens up new possibilities for single-role deployments.

这篇关于它是重用后端处理的Azure的Web角色是一个好主意？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！