Codehaus released the implementation of ESB MULE 1.0, and the ESB finally grown in the atmosphere of SOA was unveiled with a veil!
So what is ESB?
We know that the SOA architecture requires all the business-related applications in the company to provide WebService interface. So once this is implemented, all applications faced how to call these or so many interfaces, of course, the way to use the webservice to take synchronous calls, of course. At the same time, if the company has a scalability requirement, then an asynchronous message call mechanism can be taken. The ESB is the idea of the message package, and encapsulates all the calls of the service through a unified message interface. Regardless of the message is still asynchronous. In addition, ESB can also provide the same excuses such as Mail, JMS, IBM MQ, MSMQ, and more.
ESB can be used?
ESB is not universal, he is not an application framework, nor is an enterprise application solution. It is just a communication module for messaging-based calling enterprise services! You can embed it into your application framework, such as embedded Inside the Spring container, or embedded in a workflow system. Its role is to provide a framework and a convenient way to call the SOA service in your business.
What is the shortcomings from the actual business application?
ESB currently has many business programs, there are also many open source products, such as ObjectWeb, Codehaus, SourceForge has such an open source project. There is still a distance from the truly maturity, and each manufacturer is each array. The current JCP has no such technology. Draft, the standard designation also has a long distance. Of course, the current status is the same as SOA. I believe that when SOA is really popular, ESB will be more mature.
