Microsoft BizTalk Server 与 Azure AppFabric 服务总线...？
我们都知道BizTalk是微软针对ESB（企业服务总线）的商业产品。
BizTalk 通过 AppFabric 服务总线支持哪些其他现成功能。或者换句话说，AppFabric 服务总线没有为 ESB 提供哪些功能……？
就 AppFabric 服务总线而言，“服务总线”一词对于企业服务总线是否具有误导性？
We all know that BizTalk is an commercial product from Microsoft for ESB (Enterprise Service Bus).
What are other ready-made features which BizTalk supports over the AppFabric Service bus. Or in other words what does AppFabric Service Bus doesn't provide to the features of ESB ...?
Is the term "Service Bus" misleading as far as the AppFabric Service Bus is concerned with respect to Enterprise Service Bus...?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
BizTalk Server 不是“总线”，而是“代理”。 “总线”一词表示在组件之间传输数据的子系统。您可能会说 BTS 正是这样做的，但它是通过位于中心辐射模型的中间，将消息分发给适当的接收者来实现的。由于它经常在消息分发中扮演非常积极的角色，因此经纪人标签更合适。
这基本上也让您很好地了解了 Azure 服务总线和 BTS 之间的差异。 Azure 服务总线基本上只是一个数据传输子系统，使您能够跨越网络拓扑障碍将各种端点连接在一起（它使您能够使用回调通道来调用防火墙后面的服务）。
另一方面，BTS 则不这样做。相反，它具有以下 Message Broker 功能：
BTS 和 Azure 服务总线实际上是两个完全不同的事物，并且可以互补地使用。例如，很容易想到通过 Azure 服务总线连接两个 BizTalk Server。
BizTalk Server is not a 'bus', it's a 'broker'. The word 'bus' indicates a subsystem that transfers data between components. You might say that BTS does exactly that, but it does it by sitting in the middle of a hub and spoke model, distributing messages to appropriate receivers. Since it often plays a very active role in the distribution of messages, the broker label is more appropriate.
This basically also gives you a pretty good idea about the differences between the Azure Service Bus and BTS. The Azure Service Bus is basically just a data transfer subsystem that enables you to connect various endpoints together across network topology barriers (it enable you to use callback channels to invoke services behind firewalls).
BTS, on the other hand, doesn't do that. Instead, it has these Message Broker features:
BTS and the Azure Service Bus are really two entirely different things, and might be used complementarily. For example, it's easy to conceive of connecting two BizTalk Servers via the Azure Service Bus.
Microsoft 的 BizTalk 和 AppFabric Service Bus 团队实际上正在紧密合作，我们（我在那里工作）正在将 BizTalk 的功能与 AppFabric 和 Service Bus 随着时间的推移进行集成。对于 BizTalk，我们有 Windows Azure AppFabric Connect - 它允许您将 BizTalk 插入服务总线。在 PDC'10 上，我们宣布 (http://bit.ly/9gm2zI)，我们将把 BizTalk 集成功能的子集引入服务总线 - 您将听到更多关于这些功能范围的信息本年度的进程。
目前，我们认为这些产品具有高度互补性。
我希望这有帮助。
The BizTalk and AppFabric Service Bus teams at Microsoft are actually tightly collaborating and we (I work there) are integrating BizTalk's capabilities with AppFabric and Service Bus over time. For BizTalk we have Windows Azure AppFabric Connect - which lets you plug BizTalk into Service Bus. At PDC'10 we announced (http://bit.ly/9gm2zI) that we'll be bringing a subset of the BizTalk integration features into Service Bus - you'll be hearing a lot more about the extent of those capabilities over the course of the current year.
For now, think of the products as highly complementary.
I hope that helps.
今年某个时候，Azure AppFabric 推出了一项新功能，简称为“集成”，它基本上支持 Azure 上的 Biztalk 服务。
http://www.microsoft.com/windowsazure/appfabric/overview/default .aspx#top
There is a new feature coming to Azure AppFabric sometime this year simply called "Integration" which basically enables Biztalk services on Azure.
http://www.microsoft.com/windowsazure/appfabric/overview/default.aspx#top
Microsoft Biztalk Server 和 Service Bus AppFabric 乍一看可能很相似，但它们是用于不同用途的两种不同产品。
Microsoft Biztalk Server and Service Bus AppFabric might look similar at the first view but are two different products for differents usages.