将 asp.net 应用程序移植到 azure 有多大的挑战? [英] how much of a challenge is it to port a asp.net application to azure?

问题描述

我有一个部分开发的 asp.net 应用程序，但现在客户希望它在 azure 中开发.有多少现有代码可用于在 azure 中开发应用程序.

I have a partly developed asp.net application, but now the client wants it to be developed in azure. How much of the existing code can be used in developing the application in azure.

当我们尝试将现有的 asp.net 应用程序移植到 azure 时，可能会遇到哪些挑战?云计算中是否有其他替代 azure 的方法?

What challenges could we possibly encounter when we try to port an existing asp.net application to azure? Are there any other alternatives to azure in cloud computing?

推荐答案

对于 asp.net 应用程序，您当然可以将其移植到 Azure.您的核心逻辑将以相对简单的方式移植，您将获得 Azure 提供的许多好处.在 2010 年 6 月的版本中，您还将获得 .NET 4 支持以及用于调试的 IntelliTrace.

For an asp.net application, you can certainly port that to Azure. Your core logic will port in a relatively straightforward manner, and you'll gain the many benefits Azure has to offer. With the June 2010 release, you'll also have .NET 4 support, along with IntelliTrace for debugging.

但是，当您开始计划 Azure 迁移时，您需要考虑几个注意事项(没有一个是不可逾越的，有几个相对容易处理):

However, as you begin to plan your Azure migration, there are several considerations you'll need to think about (none of them insurmountable, and several relatively simple to deal with):

• 您必须处理跨 Web 角色实例的 ASP.NET 会话状态管理(不支持开箱即用，inproc 除外).您还必须设置和使用角色和成员资格提供程序(请参阅 此处 了解更多详情).您现在可以访问会话状态的 AppFabric 缓存以及 SQL Azure，这是 Windows Azure SDK+工具中包含的通用提供程序的一部分.
• 您必须检查您的 SQL 后端是否与 SQL Azure 不兼容(例如计划作业，因为没有 SQL 代理支持).SQL Azure 差异记录在此处.您还需要考虑 50GB 的 SQL Azure 大小限制，这可能需要您将内容卸载到 Azure blob 存储.您可以通过 SQL Azure 迁移向导 运行您的 SQL Server 数据库以进行兼容性测试.
• 您需要配置日志记录和诊断，最好使用 Trace 输出，以便您可以远程检索这些数据.
• 您需要考虑如何监控和扩展您的应用程序.您可以使用扩展可能需要的所有信息(性能计数器、队列长度等).查看 WASABI - 自动缩放应用程序块，企业库的一部分.您还可以订阅诸如 AzureWatch 之类的服务.
• 您需要考虑缓存，因为目前没有跨网络角色实例运行的开箱即用的缓存实现，现在作为服务提供.阅读详细信息此处，以及常见问题解答此处.
• 您需要 SMTP 支持吗?如果是这样，您应该阅读有关 这里.SendGrid 最近宣布了一个 Windows Azure 的免费层级促销.
• 您是否也在托管 WCF 服务?如果是这样，请查看本网站了解更多详情(特别是已知问题).

• You have to deal with ASP.NET Session State management across your web role instances (which isn't supported out of the box, except for inproc). You'll also have to set up and use the role and membership providers (see here for more detail). You now have access to both AppFabric Cache for session state as well as SQL Azure, part of the Universal Providers included with the Windows Azure SDK+Tools.
• You have to examine your SQL backend for incompatibilities with SQL Azure (such as scheduled jobs,since there's no SQL Agent support). SQL Azure differences are documented here. You'll also need to consider the SQL Azure size limit of 50GB, which might require you to offload content to Azure blob storage. You can run your SQL Server database through the SQL Azure Migration Wizard for compatibility-testing.
• You need to configure logging and diagnostics, preferably with Trace output, so that you can retrieve this data remotely.
• You need to think about how you'll monitor and scale your application. All information you might need for scaling is available to you (performance counters, queue lengths, etc.). Check out WASABI - the auto-scale application block, part of Enterprise Library. You can also subscribe to a service such as AzureWatch.
• You'll need to think about caching, as there's currently no out-of-the-box caching implementation that runs across instances of your web role which is now provided as a service. Read details here, as well as an FAQ here.
• Do you need SMTP support? If so, there are details you should read about here. SendGrid recently announced a free-tier promotion for Windows Azure.
• Are you hosting WCF services as well? If so, check out this site for further details (specifically the Known Issues).

所以:是的，您需要关注一些事情，但 Azure 是托管 asp.net 应用程序的绝佳平台，您应该认真考虑.

So: yes, there are some things you need to concern yourself with, but Azure is a great platform for hosting an asp.net application and you should strongly consider it.

这篇关于将 asp.net 应用程序移植到 azure 有多大的挑战?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！