Mule ESB与Spring Integration [英] Mule ESB vs. Spring Integration

问题描述

Mule ESB项目解释了其与Spring的区别集成在其网站上.但是，对于文档的 dcterms.date 2012-07-19T18:43-03:00，该文本可能已经过时了.

The Mule ESB project explains its difference to Spring Integration on its website. However, regarding dcterms.date 2012-07-19T18:43-03:00 of the document, the text might be outdated.

被引段落的要点是

• "Spring集成采用以应用程序为中心"的集成方法".
• "Spring集成不是实现共享总线，而是旨在为特定应用程序提供一点点"的ESB风格的集成."
• "Spring Integration最适合通常在内部必须集成少量组件的情况."
• "[Spring Integration有一个可用的受支持的传输器和转换器的数量很少."
• "[Spring集成的范围被故意限制为在Spring产品组合上下文中进行小规模集成."

• "Spring Integration takes [...] an 'application-centric' approach to integration".
• "Rather than implement a shared bus, [...] Spring Integration is aimed at providing 'just a little' ESB-style integration to specific applications".
• "Spring Integration is best suited to situations where a small number of components must be integrated, usually internally".
• "[Spring Integration has a] very small number of supported transports and transformers available".
• "[The] scope of Spring Integration is deliberately limited to small-scale integration within the Spring Portfolio context".

这些积分仍然有效吗?是否存在更详细的，是否最新的比较?

Are these points still valid? Does any more detailed and, if so, up-to-date comparison exist?

Mule ESB与Spring Integration

Mule ESB vs. Spring Integration

最近，在Spring产品组合中添加了一个称为Spring Integration的新组件，该组件允许在Spring Framework中创建和管理类似于ESB的功能和EIP. Spring Integration采用所谓的以应用程序为中心"的集成方法.
Spring Integration不是实现共享总线，该总线允许集中管理，管理和配置组件和系统之间的所有集成和消息传递，而是通过提供用于实现的框架为特定应用程序提供仅一点"的ESB风格的集成.常见的EIP，例如消息总线和简单的路由. 由于其范围有限，Spring Integration最适合通常必须在内部集成少量组件且所涉及的基础架构由大量其他Spring组件组成的情况.对于更复杂的事情，缺少通用总线，再加上为该年轻项目提供的少量支持的传输器和变压器，使得Spring Integration不适合该任务.
在春季环境中使用Mule ESB进行集成的优势在于，Mule ESB不仅仅是一个ESB，而是一个集成平台.尽管Spring集成的范围仅限于在Spring产品组合上下文中进行小规模集成，但Mule的故意模块化体系结构使团队可以针对任何场景快速交付最轻巧的集成解决方案，从简单的点到点集成到复杂的SOA，云计算和合作伙伴生态系统场景.

Recently, a new component called Spring Integration was added to the Spring Portfolio, which allows ESB-like functionalities and EIPs to be created and managed within the Spring Framework. Spring Integration takes what is known as an "application-centric" approach to integration.
Rather than implement a shared bus, which allows all integration and messaging between components and systems to be managed, administered, and configured centrally, Spring Integration is aimed at providing "just a little" ESB-style integration to specific applications by providing frameworks for implementing common EIPs such as a message bus and simple routing. Due to its limited scope, Spring Integration is best suited to situations where a small number of components must be integrated, usually internally, and the infrastructure in question is made up of a large number of other Spring components. For anything more complicated, the lack of a common bus, coupled with the very small number of supported transports and transformers available for the young project makes Spring Integration unsuited for the task.
The advantage of using Mule ESB to handle integration in a Spring environment is that Mule ESB is not simply an ESB - it is an integration platform. Whereas the scope of Spring Integration is deliberately limited to small-scale integration within the Spring Portfolio context, Mule's intentionally modular architecture allows teams to quickly deliver the lightest possible integration solution for any scenario, from simple point to point integration to complicated SOA, cloud and partner ecosystem scenarios.

推荐答案

完整披露:我是Spring Integration项目的现任负责人，并且已经担任提交人超过5年.

Full disclosure: I am the current Spring Integration project lead and have been a committer for over 5 years.

虽然 Spring集成确实促进了模块化和内部耦合 应用程序，它也非常适合将系统集成在一起，而无需中央ESB.我个人知道许多大型企业仅使用Spring Integration将所有业务系统集成在一起，而没有用于配置/管理的中央总线服务器.

While it is true that Spring Integration promotes modularity and loose coupling within an application, it is also very well suited for integrating systems together without the need for a central ESB. I am personally aware of a number of very large enterprises that integrate all their business systems together using only Spring Integration, with no central bus server(s) to configure/administer.

它的POJO编程模型使定制/扩展变得异常容易.如果开箱即用不支持某些传输/协议，则可以将其包装在POJO中并调用它(或考虑编写一个更正式的适配器并将其贡献给框架！).

Its POJO programming model makes it incredibly easy to customize/extend; if some transport/protocol is not supported out of the box, you can simply wrap it in a POJO and invoke it (or consider writing a more formal adapter and contribute it back to the framework!).

我们为新的重要 Spring XD Project 的基础感到特别兴奋.

We are particularly excited that it forms the basis of the new and important Spring XD Project.

您可能想看看DZone最近的

You may want to take a look at DZone's recent Guide to Enterprise Integration which talks about Spring Integration as well as the competing technologies.

这篇关于Mule ESB与Spring Integration的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！