BizTalk ESB与BizTalk的真正区别是什么? [英] What does BizTalk ESB really differentiate from BizTalk?

查看:149
本文介绍了BizTalk ESB与BizTalk的真正区别是什么?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我试图了解ESB与BizTalk本身的区别。



似乎ESB更关注管道类的东西。仍然使用BizTalk业务流程,BRE来提供工作流/决策制作的逻辑。


任何使用ESB的情况都比BizTalk基本功能更合理或方便吗? / p>


谢谢。




解决方案

企业服务总线(ESB)基本上是一种架构。这是一套规则和原则,可以通过类似总线的基础设施将大量
应用程序集成在一起。


ESB产品使用户能够构建这种类型的体系结构,但在他们这样做的方式以及他们
提供的功能。 ESB Architechure的核心概念是通过在它们之间放置通信总线来集成不同的应用程序,然后使每个应用程序与总线通信。这使系统彼此分离,允许它们在不依赖于总线上的其他系统或知道的情况下进行
的通信。 ESB的概念源于需要摆脱点对点集成,这种集成随着时间的推移变得脆弱且难以管理。点对点集成导致自定义集成
代码在应用程序之间传播,没有集中监控或故障排除的方法。这通常被称为"意大利面条代码"。并且不会扩展,因为它会在应用程序之间创建紧密的依赖关系。


BizTalk不仅仅是一种集成模式,即ESB它是一个支持许多集成模式的整体框架
和场景,它还通过其ESB工具包本身支持ESB模式。我们可以使用所有BizTalk工件并使用ESB,我们可以在这个过程中将它们绑定在一起。


当您需要基于行程的解决方案时,ESB工具包最有用,即您需要执行多个步骤的地方在做
最后一个之前,你需要灵活地管理这些步骤。在业务流程中,您需要定义模式并重新部署代码,但在ESB中,您只需管理配置中的流。


例如如果您从多个来源获取数据,我们可以在几个步骤中划分我们的解决方案


  1. 接收并加载消息
  2. 将消息转换为常见的规范格式
  3. 规范到第三方格式或数据库加载
  4. 路由到各个订户


所有这些都是独立的过程并且独立运行,在我们使用的每个步骤中本地BizTalk工件,如地图;
编排。如果添加了新的源或目标,那么拥有一个大型业务流程将是一个固定的模式并且很难更新;我们只需要在ESB行程中添加新步骤。


这里有关于ESB工具包的高级文档:

https://docs.microsoft.com/en-us/biztalk/esb-toolkit/microsoft-biztalk -esb-toolkit


示例:  https://www.codeproject.com/Articles/288285/Hello-World-in-BizTalk-ESB -Itinerary-using-a-Purch


https://www.biztalk-server-tutorial.com/2014/10/15/esb-toolkit-itineraries/




I am trying to get the idea how ESB is different from BizTalk itself.

Seems ESB is more focusing on pipeline kind of stuff. Still use BizTalk orchestration, BRE to provide workflow/decision making kind of logic.

Any case using ESB is more reasonable or convenient than BizTalk basic features?

Thank you.


解决方案

An Enterprise Service Bus (ESB) is fundamentally an architecture. It is a set of rules and principles for integrating numerous applications together over a bus-like infrastructure.

ESB products enable users to build this type of architecture, but vary in the way that they do it and the capabilities that they offer. The core concept of the ESB Architechure is that you integrate different applications by putting a communication bus between them and then enable each application to talk to the bus. This decouples systems from each other, allowing them to communicate without dependency on or knowledge of other systems on the bus. The concept of ESB was born out of the need to move away from point-to-point integration, which becomes brittle and hard to manage over time. Point-to-point integration results in custom integration code being spread among applications with no central way to monitor or troubleshoot. This is often referred to as "spaghetti code" and does not scale because it creates tight dependencies between applications.

BizTalk is a much more than just one integration pattern i.e. ESB it is a holistic framework to support many integration patterns and scenarios and it also supports ESB pattern natively through its ESB toolkit. We can use all the BizTalk artifacts and using ESB we can tie them together in the process.

ESB Toolkit is most useful when you need itinerary based solutions i.e. where you need to perform many steps before doing the final one and you want flexibility to manage these steps. In an orchestration you need to define a pattern and redeploy the code but in ESB you can just manage the flow in a configuration.

For e.g. If you are getting data from multiple sources we can divide our solution in few steps

  1. Receive and Load the messages
  2. Convert the messages to a common canonical format
  3. Canonical to third party format or database load
  4. Routing to various subscribers

All these are separate processes and behaving independently and during each step we are using native BizTalk artifacts like Maps; orchestration. Having one big orchestration will be a fixed pattern and will be difficult to update however if a new source or a target is added; we only need to add new steps in the ESB itinerary.

A good high level documentation on ESB toolkit is available here : https://docs.microsoft.com/en-us/biztalk/esb-toolkit/microsoft-biztalk-esb-toolkit

Example : https://www.codeproject.com/Articles/288285/Hello-World-in-BizTalk-ESB-Itinerary-using-a-Purch

https://www.biztalk-server-tutorial.com/2014/10/15/esb-toolkit-itineraries/



这篇关于BizTalk ESB与BizTalk的真正区别是什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆