The Mule ESB project explains its difference from Spring Integration on its website. However, for the dcterms.date of the 2012-07-19T18:43-03:00 document, the text may be outdated.
The main points of the cited paragraph are
- "Spring Integration takes an" application-oriented "integration approach."
- "Instead of implementing a common bus [...], Spring Integration aims to provide" small "ESB-style integration for specific applications."
- "Spring Integration is best suited for situations where you need to integrate a small number of components, usually inside."
- "[Spring Integration has] a very small number of supported transports and available transformers."
- "[Spring] Integration is intentionally limited to small-scale integration in the context of the Spring Portfolio."
Are these items still valid? Is there a more detailed and, if so, relevant comparison?
ESB Mule vs Spring Integration
Recently, a new component called Spring Integration has been added to Spring Portfolio that allows you to create and manage EIS-like functions and EIP in the Spring Framework. Spring Integration uses the so-called "application-oriented" integration approach.
, , , , Spring Integration , "" ESB EIP, . - Spring Integration , , , Spring. - , , , Spring Integration .
Mule ESB Spring , Mule ESB - ESB - . , Spring Integration Spring Portfolio, Mule , , SOA, .