Appfabric Azure
真实应用程序我如何使用这个应用程序结构？
我怎样才能把我的业务逻辑放在这个和这个逻辑在我的Windows Azure应用程序中使用？
谢谢
Real application how can i use this app fabric ??
How can i put my business logic in this and this logic use in my windows azure application??
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
Azure AppFabric 是一组服务，允许您利用传统上由大多数网络通用的基础设施组件提供的功能。目前，它由以下部分组成：
Azure AppFabric 服务总线 - 允许通过在云中提供集中式中继点来连接应用程序。应用程序创建到集合位置的出站连接，从而帮助缓解安全措施带来的挑战，例如入站连接的防火墙限制和通过 NAT 层的 IP 屏蔽。此功能包括“实时”选项以及动态“消息缓冲区”，以允许更多断开式通信。
Azure AppFabric 访问控制服务 - “ACS”允许 WIF 应用程序快速访问各种身份提供商并使用单一格式的声明令牌。与 ADFS 等产品结合使用，它允许云托管应用程序针对本地身份存储进行身份验证。
Azure AppFabric 缓存服务 - 目前正在公开测试中，该服务为应用程序带来了“Velocity”风格的功能。这为他们提供了分布式缓存系统以及新的会话提供程序。
2011 年将推出更多功能/服务，但这些是目前最热门的功能/服务。关于托管业务逻辑，目前 Azure AppFabric 中不提供此功能。有人提到，我们最终可能会看到将应用程序放置在“边缘”的潜力，即位于 Azure AppFabric 连接前面的服务器，但没有预计时间，甚至没有明确承诺这将会发生。
The Azure AppFabric is a collection of services that allow to you leverage functionality traditionally provided on premise by infrasture components common to most networks. Currently, it consists of the following:
Azure AppFabric Service Bus - allows for connection of applications by providing a centralized relay point in the cloud. Applications create outbound connections to the rendezvous location, thus helping mitigate the challenges posed by security measures like firewall restrictions on in-bound connections and IP masking via NAT layers. This feature includes both 'real time' options as well a 'message buffer' dynamic to allow for more disconnected style communication.
Azure AppFabric Access Control Service - the "ACS" allows WIF applications to quickly access various identity providers and consume a single format of claims token. Used in conjunction with products like ADFS, it allows cloud hosted applications to authenticate against on-premise identity stores.
Azure AppFabric Cache Service - currently in public testing, this service brings the "Velocity" style functionality to applications. This provides them with a distributed cache system as well as a new session provider.
There's more features/services coming in 2011, but these are the hot ones currently. Regarding hosting your business logic, this is not something that is currently available in the Azure AppFabric. There's been mentions that we may eventually see the potential for placing applications "on the edge", meaning the servers that front the Azure AppFabric connections, but no ETA or even firm commitment that this will happen.
您可以在 Windows Azure 中以 Web 或辅助角色的形式实现业务逻辑，具体取决于您是否需要同步或异步。
您可以使用服务总线来呈现业务逻辑，不过您也可以在本地实现逻辑并通过服务总线来呈现它们。
You can implement your business logic in Windows Azure, in a web or worker role depending if you need it to be synchronous or asynchronous.
You can surface the business logic using the service bus, though you could also implement your logic on premise and surface them via the service bus.
AppFabric 不是业务逻辑层。将 AppFabric 视为横切，或应用程序不同部分之间的粘合。
目前，业务逻辑位于 Web 或辅助角色等组件中，或者可以使用 AppFabric 服务总线在互联网上公开的本地应用程序中。
在未来的版本中，AppFabric 将发布“复合应用程序”，简而言之，它似乎允许您部署托管的 WCF/WF 工作流服务，从而形成更好的“业务引擎”。但现在我认为您可能只在网络角色中使用工作流服务。
AppFabric is not a business logic layer. Think of AppFabric as cross-cuts, or glue between different parts of your application.
For now Business logic goes in components like a web or worker role, or an on premise app which you could expose on the internet using AppFabric Service Bus.
In a future release, AppFabric will release "Composite Apps" which in a nutshell seem to allow you to deploy managed WCF/WF workflow services, which makes for a better "business engine". But for now I think you could probably just use Workflow services in a web role.