Comparison of several ESB Software

A reference on the difference between messagebroker and ESB: "If we specifically compare the ESB product with the message bus product (activemq?) in the traditional EAI ?) There are three main differences between the two. First, ESB is based on the SOA business-oriented philosophy, so itMainly through ConfigurationInstead of programming. Second, ESB must have the ability to establish intercommunication mechanisms between different protocols, including traditional message mechanisms (JMS) and Web service interfaces (WS). Third, in addition to the message (service) proxy method, ESB must also provide service lifecycle management for SOA service governance, rather than simply filtering, forwarding, routing, and service lifecycle management, it refers to service release, registration, use, promotion, benefit statistics, upgrade, etc.

About the efficiency of ESB: "ESB adopts a lightweight distributed architecture. A centralized switch center makes sense only when every interaction between programs must be converted to a standard format. ESB (such as Iona artix) can allocate more processing logic to the endpoint. This is similar to the difference between a large host and a modern distributed system architecture. In a broad sense, the most important technologies of ESB are inseparable from web services, such as WSDL (Web Service Description Language) and UDDI (Unified discovery, description, and integration) and soap (Simple Object Access Protocol). This technology is currently in a stable development stage, and the development of WS * is in an unstable process of integration and penetration. In addition, some related technologies are active, such as the process-related BPEL (Business Process Execution Language), the security-related SAML (Security asserted Markup Language), and the XML-processed XQuery; service component model SCA/SDO (service component architecture/service data object) and jbi (Java business integration ".

The above should be translated from foreigners. English articles, especially technical articles, are very different from Chinese language habits, we feel that the English technical articles are inexplicably cool in the areas where they should be detailed.

 

For more information about camel, see http://www.javaeye.com/wiki/interview/1858-apache-camel. When talking about the advantages of camel over other ESB, jnn focuses on two points: first, camel is lighter; second, camel supports the Java syntax-based transport configuration (for example, forwarding cxf: From ("JMS: // XXXX") after receiving a message from JMS "). processor (New myprocessor ()). to ("cxf: // XXXX "))

For springintegration, spring seems to be doing a little too much. Spring's goal seems to be to provide developers with a more lightweight spring style around IOC, for example, springmvc compares struts and spring persistence with hibernate. Spring, as a non-invasive, lightweight framework, can be well integrated with SCA. The following text is from the original version of the SCA White Paper.

SCA views spring as a natural partner which can be used as a component implementation technology. the Spring framework can be used to create components and wire them within a module using its dependency injection capabilities. SCA may be used to extend the capabilities of spring components by publishing spring beans as entry points to be accessed as services by other modules as well as by providing spring beans with service references wired to services other modules.

It can be seen that SCA and spring are closely related and can complement each other. I believe that SCA and spring will be more closely integrated in the future to better utilize their respective advantages.

Idea of SCA and spring: dependency injection --

 

 

According to alloyer's opinion:Camel is an integrated framework that focuses on message routing. If you want to develop your own ESB, you can consider developing it based on camel. Some mule transmitters have some bugs. That is to say, the code quality is not as high as that of Apache projects. mule neither supports jbi nor SCA. Mule is a lightweight ESB that provides little code intrusion. We recommend mule for entry-level and development efficiency. ServiceMix is recommended for projects with high load and high requirements.

Mule ranks first in ESB project activity on SourceForge, and mule should be opensymphony, one of the four major open-source Java systems. Now, mule has changed from mulesource to mulesoft, And the paid Enterprise Edition has also been released, I don't know which one is better than pure open source.