|Product Description and positioning
||Lightweight message framework and integration platform; EIP-based implementation; Core Component UMO for integration logic; supports more than 20 transmission protocols (such as file, FTP, UDP, SMTP, Pop, HTTP, soap, and JMS ). It also integrates many popular open-source projects, such as spring, activemq, cxf, axis, and drools.
||It is an implementation of jbi specifications, including well-known jbi components. These components support multiple protocols, such as JMS, HTTP, FTP, and file. EIP, rules, and scheduling are also implemented. Apacheservicemix also integrates other open source projects, such as Apache, Apache, activemq cxf, apahe camel, Apache ode, and Apache Geronimo.
||Open ESB can run in the glassfish Application Service supported by Sun. Sun's netbeans ide also provides a drag-and-drop development tool for open ESB, Which is unmatched by other Open-Source ESB. Although mule also provides eclipse-based plug-in tools, it is still not powerful enough.
||JBoss ESB is based on JBoss's ESB product Rosetta. JBoss ESB uses jbossmq as its message layer and uses JBoss Rules to provide its routing function,
Provide service orchestration for jbpm. JBoss ESB is an EAI system platform proposed by the JBoss community for SOA. It provides many functions that EAI should possess, for example, business process monitoring, integrated development environment, workflow user interfaces, business process management, distributed computing architecture, and functions as application containers.
|Wso2 is based on Apache synapse. It can be used to connect, manage, and convert services between Web Services, rest/pox services, and legacy systems. It also provides an Ajax-based ESB console to perform statistical analysis, management (add, delete, and modify) on its configuration files, and specify to execute the corresponding configuration files. This is rare in Open-Source ESB.
||Openadaptor is located in the EAI (Enterprise Application Integration) software. It supports various transmission protocols, such as JMS, JDBC, ibm mq series, tibco rendezvous, TCP/IP sockets, soap, HTTP, and file.
|Defects and deficiencies
||There is no way to hot deploy new integration processes.
||If you want to further expand the bus, you need to study the source code and examples in depth. Of course, the foundation of all this is a comprehensive understanding of the jbi specifications.
||It is difficult to expand openesb according to its own requirements unless the source code of openesb is comprehensively analyzed.
||Compared with the above bus, its technical architecture solution is the most independent. In addition to supporting the J2EE standard, the jbi standard does not overlap. Of course, there is no standardized message routing, service engine, and binding component in the jbi standard.
||Mule provides a Java-centered model that supports jbpm and message independence without hot deployment.
Advantages of mule:
1. The architecture is simple, clear, and easy to use;
2. It has a wide range of transmitters, routers and converters and is easy to expand;
3. mule does not need to convert messages into a uniform format, but only converts messages as needed, improving performance;
4. You do not need to pay attention to the mule code during development. You only need to configure the mule to expose the service, reducing the intrusion;
5. Clear and complete documents;
Disadvantages of mule:
1. No ESB specifications were implemented (but following enterprise intergration patterns and Seda standards (staged event-driven architecture ));
2. Hot deployment is not supported (supported by the Enterprise Edition );
The reason mule chooses not to implement jbi: To Keep It lightweight and flexible, improve efficiency and ease of use.
Mule provides a jbi adapter to maintain connectivity with the jbi container.
|ServiceMix provides support for jbi and BPEL integration. It focuses on XML messages and hot deployment features.
Advantages of ServiceMix:
1. Based on jbi specifications;
2. Hot deployment is supported;
3. Support for camel (you can use DSL to develop the integration process );
Disadvantages of ServiceMix:
1. The jbi specification makes it cumbersome to use, and the jbi specification has not received much favor, and its future is unknown;
2. Too much dependency on xml configuration;
3. All messages must be standardized to generate and parse XML files, resulting in performance degradation;
4. The messageexchangelistener interface must be implemented during the development process to receive and process the above standard messages, which is highly invasive;
5. Incomplete and unclear documents;