Azure 可以与 Amazon 互操作吗？
我有一个问题，云厂商是否有互操作机制。例如，我正在开发 WCF 服务并成功托管在 Azure 中。长期使用 Azure 后，我可以使用相同的代码在 AWS 中部署它吗？有可能吗？两者的API部署是否匹配？如果没有，那么在切换其他云供应商（如 Salesforce.com、OpenStack 等）时托管相同服务需要额外注意什么？
I have a question about whether cloud vendors have an inter-operable mechanism. For example, I am developing a WCF service and hosting in Azure successfully. After a pro-long time using Azure, can I use the same code for deploying it in AWS? Will it be possible? Does the API of both matches the same for deploying? If not, what are all the extra care needed for hosting the same service when switching over other Cloud Vendors like Salesforce.com, OpenStack, etc.,
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
一般来说，您不能只是将为一个云平台开发的内容放到另一个云平台上：它们具有不同的功能集并公开不同的 API。然而，您编写的代码越低级，您就越有可能找到具有非常相似 API 的另一个供应商，因为虚拟化基础架构比虚拟化 CMS 应用程序更简单（并且更接近标准化）。
如果您仅使用 IaaS，您可能可以相当快地移植，但您必须做更多工作来制作应用程序。如果您使用 PaaS（或 SaaS！），那么您会更加锁定，但您会获得更多快速开发支持：支持平台既是增值又是锁定，您不会两者兼而有之。
In general, you can't just take what you develop for one Cloud platform and put it on another: they have different functionality sets and expose different APIs. However, the more low-level you make your code, the more likely it is that you'll find another vendor with a very similar API, since virtualizing infrastructure is simpler (and closer to standardized) than virtualizing a CMS application.
If you're using just IaaS, you can probably port fairly rapidly but you have to do more work to make your application. If you're using PaaS (or SaaS!) then you're more locked-in but you get more support for developing rapidly: it's that support platform which is both the value-add and the lock-in, and you won't get one without the other.
如果您使用 Azure Web 角色来托管 WCF 服务，那么从部署的角度来看，您在使用 AWS 时不会遇到太多问题。您只需使用适用于 .NET 的 AWS 开发工具包（也称为发布到 AWS CloudFormation）提供的设施即可。当然，如果您已将 Azure 诊断和所有 Azure 服务与相关 AWS 服务一起使用，则必须更改日志记录部分。去年我们多次这样做，而且效果很好。
对于辅助角色来说，事情没那么简单，因为在 Azure 中，它们可以像 Web 角色一样轻松部署，但在 AWS 中，您无法从 Visual Studio 直接部署，因此您必须使用 Windows 服务或其他方式进行一些手动工作
If you're using an Azure web role for hosting your WCF service then from deployment point of view you will not have many problems with AWS. You'll simply use facilities offered by AWS SDK for .NET (aka Publish to AWS CloudFormation). For sure you'll have to change the logging part if you've used Azure Diagnostic and alla Azure services with related AWS services. We did this multiple times in the last year and it works.
For worker role it's not so simple because in Azure they are easily deployed like web role, but in AWS you haven't direct deployment from Visual Studio so you have to do some manual work using Windows Services or something else