在 Azure 上托管托管应用程序
我们有一个 ASP.net Web 应用程序，希望在 Azure 上托管以扩展到数千个并发用户。还有一堆用 .NET 编写的应用程序和服务，Web 应用程序使用 TCP/IP 或 .net 远程处理来访问这些应用程序和服务，以处理长时间运行的进程。例如，媒体转码器服务器、系统监视器、图像服务器、调度服务器仅举几例。
问题：
- Azure 允许我们在 Azure 实例上安装这些吗？
- 假设站点需求增长并且 Azure 需要扩展到多个实例，我们仍然只需要这些服务器的一个实例。我们如何获取主实例的 IP？
We have an ASP.net web application and would like to host on Azure to scale to thousands on concurrent users. Also have a bunch of application and services written in .NET that the web app accesses using TCP/IP or .net remoting which handle long running processes. For example a media transcoder server, a system monitor, image server, schedule server just to name a few.
Questions:
- Will Azure allow us to install these on the Azure instance?
- Suppose demand for the site grows and Azure needs to scale to multiple instances, we would still only require one instance of these servers. How would we even get the IP of the main instance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
自从 Windows Azure 推出 完全信任支持，您几乎可以在 Azure WebRole 或 WorkerRole 上运行任何应用程序。主要困难是您需要重新打包适用于 Windows Azure 的应用程序。如果您的应用程序是用 .NET 编写的，那么该端口应该相当简单。
对于长时间运行的进程，队列/工作模式应该非常方便，您可以检查 Lokad.Cloud 的实际实施。
Since Windows Azure introduced full trust support, you can run virtually any app on to of the Azure WebRole or WorkerRole. The main difficulty being that you need to repackage your apps for Windows Azure. If your apps are written in .NET, then the port should rather straightforward.
Concerning long running processes, the Queue/Worker pattern should be very handy, you can check Lokad.Cloud for a practical implementation.
您必须重写现有应用程序才能在 Azure 上运行。
听起来您正在寻找一种在云中运行实例的方法，请查看：
http ://aws.amazon.com/ec2/instance-types/
You would have to rewrite existing applications to run on Azure.
Sounds like you are looking for a way to run instances in the cloud, have a look at:
http://aws.amazon.com/ec2/instance-types/
您需要重新构建服务以在 Azure 中作为辅助角色运行，而不是在 Azure 上安装服务 - 可能不会太困难，因为模式非常相似。然而，微软很可能会在明年初向 Azure 添加“VM 角色”，以与亚马逊的 EC2 实例竞争。实现虚拟机角色后，您可能可以对它们执行任何您喜欢的操作，即安装您的服务。
Rather than installing your services on Azure, you would need to re-architect your services to run as Worker Roles within Azure - might not be too difficult as the patterns are very similar. However, Microsoft will very likely be adding "VM Roles" to Azure early next year to compete with Amazon's EC2 instances. When VM roles are implemented, you could likely do whatever you like to them, i.e. install your services.
令人惊讶的是，Azure 是根据您的用例构建的。您确实必须为 Azure 重新打包服务（正如人们所提到的）。我推荐 Microsoft PDC 获取 Azure 信息。他们有大量精彩的演示文稿、文章、视频和示例可供参考。
Azure 有一个很好的系统来将服务映射到 IP 地址。这称为 AppFabric 服务总线。当您连接到服务总线时，您作为服务的使用者或服务的提供者进行连接。总线负责将消费者和提供者映射在一起。您甚至可以让消费者或提供商在世界各地并在防火墙内运行。这听起来正是您正在寻找的。有了这个系统，您根本不必担心IP地址。您使用应用程序 ID 和令牌进行连接，然后按名称请求服务。 Azure 负责剩下的事情。
要增加或减少每个角色的实例数量，您所需要做的就是编辑服务配置文件以更改相应角色的实例数量并将更改发送到 Azure。它会自动调整实例。
雅各布
Amazingly enough, Azure was built with your use case in mind. You do have to repackage your services for Azure (as people have mentioned). I recommend Microsoft PDC for Azure information. They have tons of great presentations, articles, videos, and samples to start from.
Azure had a nice system for mapping services to IP addresses. This is called the AppFabric Service Bus. When you connect to the service bus, you connect as either a consumer of the service or a provider of the service. The Bus takes care of mapping consumers and providers together. You can even have consumers or providers running all around the world and inside firewalls. This sounds like exactly what you are looking for. With this system, you do not have to worry about IP addresses at all. You connect with you application ID and token and then request a service by name. Azure takes care of the rest.
To scale the number of instances of each role up or down, all you have to do is edit the service configuration file to change the number of instances of the appropriate roles and send the changes to Azure. It will automatically adjust the instances.
Jacob