Today, the concept of SOA is gradually clear.
The concept of ESB has been arguing for many years, and there is still no conclusion.
I personally think that ESB is originally an abstract concept with rich connotations and different meanings in different occasions. Therefore, it should be understood from different angles.
1. SOA and ESB have always been two acronyms without a clear concept
The reason is that the connotations of these two words are too rich to be explained in a sentence or two, and the meaning of the word is different in different places.
SOA----Service-Oriented Architecture, actually emphasizes a kind of architecture of software, a relatively stable structure that supports software operation. The surface meaning is so, in fact, SOA is a kind of solution to system integration through service integration. Thought. It is not a specific technology, but a strategy and an idea in essence.
ESB----Enterprise Service Bus, like a "smart" pipe, used to connect various "dumb" nodes. In order to integrate services of different systems and different protocols, ESB does the work of message conversion, interpretation and routing, so that different services can be interconnected.
At present, the exact concept of ESB and SOA still does not exist. But it can be clearly said that SOA is a service integration idea, and its different implementation methods may vary greatly. At present, the most common implementation methods of SOA are SCA and JBI.
2. What exactly is an ESB?
There are also great differences in understanding and viewpoints on this issue among major manufacturers.
IBM, Oracle, etc. think that ESB is a mode of connecting services, but some open source organizations and other manufacturers think that ESB is a product and provide the implementation of ESB connection solutions, which can be considered as middleware or as middleware. is the component tool.
In this regard, my personal opinion is more inclined to the former. ESB is a model, and there are many ways of implementing ESB, which can be called ESB products. Of course, the meaning of ESB is different in different occasions and needs to be identified.
3. Why ESB and SOA stick together
Usually, these two nouns are always inseparable, and the topic of discussion is "you have me, I have you".
Why is this so?
Is ESB SOA?
What is the subtle relationship between the two?
When in doubt, keep reading:
First of all, ESB is not SOA. The most common implementation methods of SOA are SCA and JBI, and the implementation of SCA requires ESB, on the contrary, JBI does not need ESB. You can refer to my article on the analysis and interpretation of JBI and SCA.
Secondly, because IBM and Oracle (the company that acquired BEA and SUN) both respect the SOA of the SCA model, SCA has actually become the de facto standard of SOA. When it comes to SOA, the first thing that comes to mind is the SCA model.
Finally, ESB is an indispensable part of the realization of SCA architecture. ESB products have no meaning except for specific applications. The role of ESB is to realize the intermediary of intelligent integration and management between services. All registered services of the integrated system can be accessed through the ESB.
Fourth, the characteristics of ESB
ESB is a standard way of integration between loosely coupled services and applications. It can act on:
Service Oriented Architecture - Distributed applications are composed of reusable services
Message-Oriented Architecture - Send and receive messages between applications via ESB
Event-driven architecture - asynchronously generating and receiving messages between applications
ESB is an intermediary that realizes intelligent integration and management between services in SOA architecture.
(Quoted from this paragraph: IT Expert Network
http://whatis.ctocio.com.cn/searchwhatis/179/7332679.shtml
)
---------------------
When learning a new thing, understanding is the most important thing. Only by constantly learning and understanding can we grasp its characteristics, functions, attributes, etc., and make reasonable use of it on the basis of understanding. Any misunderstanding can only lead to deviations from principles and standards.
http://lavasoft.blog.51cto.com/62575/165597/