为什么2种的AppFabric的？ [英] Why 2 kinds of AppFabric?

问题描述

我看到，我们现在既有的Windows Server AppFabric的和Azure的AppFabric的。这仅仅是微软营销部门命名空间冲突还是这些​​技术有着共同的接口？有人告诉我，是有人可以运行本地生产服务器上使用的Azure AppFabric的应用程序，然后部署目标更改为Azure的需求。这是可能的，并与Azure的许可是否一致？如果是这样，我们可以使用Windows Server AppFabric的本地服务器上在这种情况下？

I see that we now have both Windows Server AppFabric and Azure AppFabric. Is this just a namespace collision in the Microsoft marketing department or do these technologies share common interfaces? Someone told me that is was possible to run an application using Azure AppFabric on a local production server, then change the deployment target to Azure on demand. Is this possible and consistent with Azure licensing? If so, can we use Windows Server AppFabric on the local server in this scenario?

我认为数据服务都在云计算的一致性进行维护，但进出Azure中的移动UI和业务逻辑将减少在非活动期间的托管费用的好方法。

I assume that data services would have to be maintained in the cloud for consistency, but moving the UI and business logic in and out of Azure would be a great way to cut down on hosting costs during periods of inactivity.

推荐答案

不幸的是，微软已决定参考这两个东西作为一种应用面料。菲尔写Azure的版本是在Azure云计算和Windows Server版本是你自己的机器。

It is unfortunate that Microsoft have decided to refer to both of these things as a type of App Fabric. AS Phil writes the Azure version is for the Azure Cloud and the Windows Server version is for your own machines.

不幸的是它们之间的功能是不同的，所以你不能简单地从一个到另一个移动。我说不幸的，因为我们想使用Windows Server AppFabric中的一部分，分布式缓存（previously被称为速度，一个更好的名字），在云上，这是尚未公布。

Unfortunately the features between them are different and so you cannot simply move from one to the other. I say unfortunate as we wanted to use a part of the Windows Server AppFabric, the distributed Cache (previously referred to as velocity, a much better name), on the cloud, and it is not available yet.

这篇关于为什么2种的AppFabric的？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！