Mule ESB 与 Spring 集成

Question

关闭。这个问题需要更多 focused .它目前不接受答案。












想改进这个问题？更新问题，使其仅关注一个问题 editing this post .

7年前关闭。




Improve this question




Mule ESB 项目解释了它的 difference to Spring Integration在其网站上。但是，关于 dcterms.date 2012-07-19T18:43-03:00文档中的文本可能已过时。

引用段落的要点是

“Spring Integration 采用 [...] 一种‘以应用程序为中心’的集成方法”。

“而不是实现共享总线，[...] Spring Integration 旨在为特定应用程序提供'一点点' ESB 风格的集成”。

“Spring Integration 最适合必须集成少量组件的情况，通常是在内部集成”。

“[Spring Integration 有] 非常少的支持传输和转换器可用”。

“[The] Spring Integration 的范围被故意限制为 Spring Portfolio 上下文中的小规模集成”。

这些点还有效吗？是否存在更详细的比较，如果有的话，是否存在最新的比较？

Mule ESB vs. Spring Integration

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.

Answer 1

全面披露:我目前是过去的 Spring Integration 项目负责人，并且已经做了 10 多年的提交者。
虽然 Spring Integration 是真的促进模块化和松耦合在 内作为一个应用程序，它也非常适合将系统集成在一起而无需中央 ESB。我个人知道许多非常大的企业只使用 Spring Integration 将他们所有的业务系统集成在一起，没有中央总线服务器来配置/管理。
它的 POJO 编程模型使定制/扩展变得异常容易；如果某些传输/协议(protocol)不支持开箱即用，您可以简单地将其包装在 POJO 中并调用它(或考虑编写更正式的适配器并将其贡献回框架!)。
我们特别兴奋的是，它构成了新的重要 Spring Cloud Stream 的基础。 .
你可能想看看 DZone 最近的 Guide to Enterprise Integration其中谈到了 Spring Integration 以及竞争技术。