Azure 上的 WCF 服务

发布于 2024-12-08 14:39:21 字数 311 浏览 1 评论 0原文

我计划将我的所有 VPS 功能迁移到我的 Azure 订阅。 我有 3 年的免费 bizSpark 订阅,它为我提供了 20 个核心、6 个托管服务和 5 个存储。我相信这是两个小例子。

我的主要目标是转移我目前在 IIS7.0 服务器上运行的 10 个左右 WCF 应用程序。

我可以使用 Azure 托管多少个 WCF 服务?

我整天都在阅读和使用 Azure,但仍然完全搞不清楚它的作用。从我目前的情况来看,似乎每个 WCF 服务都需要自己的托管服务,而我只有 6 个?或者我感到困惑了。 WCF 服务是否需要放入“托管服务”中?

谢谢。

I am planning to migrate all my VPS functions to a my Azure subscription.
I have the free 3 year bizSpark subscription which gives me 20 cores, 6 hosted services and 5 storages. I believe this is 2 small instances.

My Main aim is to transfer my 10 or so WCF applications which I currently run on a IIS7.0 server.

How many WCF services am I able to host with my Azure?

Ive been reading about and playing with Azure all day, but still completely confused what it all does. From my current playing, it seems each WCF service needs its own hosted service, to which i only ahve 6 of? or am I getting confused. Do the WCF services need to be put in a 'hosted service'?

Thanks.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

任性一次 2024-12-15 14:39:21

让我看看是否可以帮忙:

  • Windows Azure 是一个平台,您可以在其中将应用程序部署到云,而不必担心为底层基础设施或功能(例如缓存、身份管理等)构建管道。
  • 每个 Windows Azure 订阅都有多个部署槽或托管服务。此数量限制为 6 个,这意味着您最多可以部署六个完整的部署包(每个部署包包含一个或多个虚拟机实例)。
  • 每个虚拟机也称为角色,占用一定数量的核心。小角色使用 1 个核心,中型 = 2 个,大型 = 4 个,超大型 = 8 个。
  • BizSpark 每月为您提供 1500 个核心小时。如果您运行小型角色实例整整一个月,您将消耗不到 750 小时。因此,您可以 24x7 运行 2 个小型角色实例,并且仍然符合 1500 个包含的核心小时数。
  • 您的帐户上限为 20 个核心,这意味着您可以将角色实例增加到 2 个以上。但是,如果您 24x7 运行,您将开始产生成本。如果您将每月消耗控制在 1500 个核心小时以下,那就没问题。因此,如果您运行所有 20 个核心 24 小时,您将消耗 20x24=480 个核心小时。按照这个速度,您将在大约 3 天内用完包含的时间。
  • 每个角色本质上都是 Windows Server 2008 R2。 Web 角色与辅助角色的不同之处在于 Web 角色启用了 IIS。
  • 每个部署(例如托管服务)可以公开最多 25 个面向外部的端点(例如 tcp、http 或 https 端口)。您可以在任何公开的端口上托管 WCF 服务
  • 您可以将所有 WCF 服务托管在单个角色中,或将它们放置在单独的角色中。你的选择,真的。托管单个角色的成本较低,因为您现在可以在 2 个实例中运行整个服务堆栈。缺点是,如果您有一个非常繁忙的服务,而其余服务相对空闲,则繁忙的服务可能会导致其他服务挨饿。因此,有时将服务分成不同的角色并相应地进行扩展是有益的。
  • 请注意,我说过您可以在 2 个实例中运行所有内容。如果您仅在一个实例中托管,则每当该实例重新启动时(例如硬件故障、角色实例操作系统升级或主机操作系统升级),您都会偶尔发生停机。

您确实应该下载Windows Azure 平台培训套件。在那里,您将找到易于遵循的实验室,引导您完成所有基础知识、托管服务、部署到多个角色等。

祝您好运!

Let me see if I can help out a bit:

  • Windows Azure is a platform where you can deploy applications to the cloud and not worry about building the plumbing for underlying infrastructure or features such as caching, identity management, etc.
  • Each Windows Azure subscription has multiple deployment slots, or Hosted Services. This is limited to 6, meaning you can deploy up to six complete deployment packages (with each deployment package consisting of one or more Virtual Machine instances).
  • Each Virtual Machine, also called a Role, takes up a certain number of cores. A Small role uses 1 core, medium=2, large=4, and extra large=8.
  • BizSpark gives you 1500 core-hours monthly. If you ran a Small role instance for an entire month, you'd consume just under 750 hours. Thus, you can run 2 Small role instances 24x7 and still fit within the 1500 included core-hours.
  • Your account is capped at 20 cores, meaning you can crank up your role instances beyond 2. However, if you ran this 24x7, you'd start incurring costs. If you keep your monthly consumption under 1500 core-hours, you're fine. So, if you ran all 20 cores for 24 hours, you'd consume 20x24=480 core-hours. At that rate, you'd consume your included hours in about 3 days.
  • Each Role is essentially Windows Server 2008 R2. A Web Role differes from Worker Role in that a Web Role has IIS enabled.
  • Each Deployment (e.g. Hosted Service) may expose up to 25 externally-facing endpoints (e.g. tcp, http, or https ports). You may host a WCF service on any of your exposed ports
  • You may host all of your WCF services in a single role, or place them in separate roles. Your choice, really. It's less expensive to host in a single role, as you can now have your entire service stack running in 2 instances. The downside is that, if you have one very busy service, and the remaining services relatively idle, the busy service can starve the other services. So sometimes it's beneficial to separate services into different roles, and scale accordingly.
  • Note that I said you can run everything in 2 instances. If you only host in one instance, you will incur occasional downtime whenever that instance is rebooted (e.g. hardware failure, Role Instance OS upgrade, or Host OS upgrade).

You should really download the Windows Azure Platform Training Kit. There, you'll find easy-to-follow labs that walk you through all the basics, hosting services, deploying to multiple roles, etc.

Good luck!

淡笑忘祈一世凡恋 2024-12-15 14:39:21

您可以使用 Azure 做任何事情,因此请不要不知所措。

我们将从您的订阅附带的内容开始。所有这些核心、服务和存储帐户都是您可以部署的,但这与您免费获得的内容无关,任何注册帐户的人都可以访问这些内容。您可以将角色部署到使用两个额外小型实例的服务之一,并且无需付费。如果您部署的内容超过此数量,即使它当前没有运行,您也会被收取费用。

对于您的 WCF 服务,如果您当前将它们全部部署在一个 IIS 机器上,您应该能够创建一个 Web 角色并将其配置为 托管多个站点。但是,如果您只有超小型实例,根据您的应用程序使用的资源,它们的性能可能不会很好(例如,超小型实例只有 750MB 的 RAM)。如果是这种情况,您将需要创建多个 Web 角色,并根据需要在每个 Web 角色中托管尽可能多的应用程序。

You can do just about anything with Azure so try not to get overwhelmed.

We'll start with with what comes with your subscription. All of those cores, services and storage accounts are what you have available to deploy to, but that is not related to what you get for free, anyone who signs up for an account gets access to those. You can deploy a role to one of those services which uses two extra small instances and not get charged. If you deploy anything more than that, you will get charged, even if it's not currently running.

For your WCF services, if you currently have them all deployed on just one IIS box, you should be able to create one Web role and configure it to host multiple sites. However, if you only have extra small instances, depending on the resources your applications use, they may not perform very well (e.g. extra small instances only have 750MB of ram). If this is the case you will need to create more than one web role and host as many of your applications in each web role as you need.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文