具有映射支持的.NET ESB

发布于 2024-10-20 09:36:43 字数 304 浏览 1 评论 0原文

我们正在构建一个企业集成系统,并且正在积极评估一些 .NET ESB。我们与许多外部系统交互 - 通过各种协议公开数据 - 主要是 http post、http get、TCP/IP、Webservice、Meessage Queue。因此,我们需要这些系统的同步和异步映射支持。

Biztalk + ESB 工具包是一种选择 - 想了解更多选择吗?

我们还研究了 NServiceBus 和 MassTransit - NServiceBus 和 MassTransit 之类的问题需要开发自定义适配器来来回传送消息。没有现成的功能可用于与外部服务进行映射。

We are building an enterprise integration system, and are in the active process of evaluating some .NET ESBs. We interface with a number of external systems - which exposes data via a wide range of protocols - mainly http post, http get, TCP/IP, Webservice, Meessage Queue. So, we need sync and async mapping support for these systems.

Biztalk + ESB Toolkit is one option - Would like to hear further options?

We had a look at NServiceBus and Masstransit as well - The problem with the likes of NServiceBus and MassTransit requires development of custom adapters for pumping the messages back and forth. There is no out of the box functionality available for mapping with external services.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

终遇你 2024-10-27 09:36:43

对于集成部分(多协议支持),您可以使用 BizTalk 或 WCF,但 BizTalk 拥有适用于不同技术的最全面的连接器集。

对于映射,BizTalk 映射器(或其他图形工具)适用于简单情况,但这些工具很快会导致非常复杂的映射(难以开发/读取/修改),甚至对于来源很少的情况的复杂性。因此,您还应该考虑另一种映射解决方案,例如 XSLT。

对于 ESB 部分,我会避免使用 ESB Toolkit,因为它是一个复杂、不成熟且脆弱的框架,因此在项目中使用它是有风险的,并且可能会导致更复杂的解决方案。

NServiceBus 似乎是一个更好的解决方案,并且可以很好地与 BizTalk 集成部分配合。

For the integration part (multi protocol support) you could use either BizTalk or WCF, but BizTalk has the most comprehensive set of connectors for different technologies.

For mapping, the BizTalk mapper (or another graphical tool) will work for simple cases, but these tools quickly lead to very complex maps (hard to develop/read/modify), for cases with even minor sources of complexity. So you should also look at another solution for mapping, such as XSLT.

For the ESB part, I would avoid the ESB Toolkit, because it's a complex, immature and fragile framework, so using it in a project is risky and will probably lead to a more complex solution.

NServiceBus would seem like a better solution and can fit nicely with BizTalk for the integration part.

后来的我们 2024-10-27 09:36:43

我建议您查看《企业集成模式》一书 (http://www.enterpriseintegrationpatterns.com/),其中包含许多服务总线提供的企业集成消息传递方法。

请注意,您应该考虑拆分同步和异步操作,因为您可能不想使用消息传递进行同步操作。它们确实非常适合异步操作。情况可能是这样,您将受益于不止一种方法,具体取决于您的设置(例如 NServiceBus 和 WCF)。

I would recommend checking out the Enterprise Integration Patterns book (http://www.enterpriseintegrationpatterns.com/), which has the messaging approach to enterprise integration, as offered with many service busses.

Just as a note, you should consider splitting the sync and async operations, as you probably don't want to use messaging for sync operations. They do fit async operations perfectly. It could be the case, that you will benefit from more than one approach, depending on your setup (like NServiceBus and WCF).

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文