Service-Oriented Architecture (SOA) -- (1) objectives and core concepts

What is SOA?

I often hear that people talk about things together with SOA, such as whether SOA can replace object-oriented (OOP) or which of the two is more advantageous? Direct answers are difficult. For example, the answer may be easier to understand. The child asked you to do your homework seriously? Or should I report to science during the college entrance examination? If you don't have a mind, it's just a meaningless question. (To be exact, oop and SOA are still associated, just as if you can study hard and report to science at the college entrance examination .)

Service-Oriented Architecture refers to a system architecture. Its research field is the "architecture" paradigm of large-scale distributed systems. Oop refers to the "programming" paradigm in the specific development process of the program. In other words, we talk about OOP in a specific software, but we are talking about software and software, when it comes to the relationship between systems, we will use the concept of SOA to help us deal with the relationship between them (each system. The last thing you should talk about is that unless you are only responsible for encoding, you need to understand the two.

Why SOA

"Not the strongest or smartest race, but the most responsive race ." -- Darwin species Origin

Presumably, the above may make readers feel shocked. I cannot help but ask what is the relationship between software design (or large-scale distributed software design) and evolution? In fact, they are the same. Every species has its own life cycle, "resource race, survival of the fittest". The same is true for software, and each software has its own life cycle, the life cycle of the software will naturally be reasonably extended if it can meet the requirements of users and be able to get along with the surrounding environment (other software. The present age is no longer the beginning of life. A single species exists and it is time to ignore the existence of other creatures. Similarly, it is impossible for enterprises to develop a comprehensive set of software, regardless of their capital or time. What is most likely to happen is that old systems are constantly emerging in new systems, old and new intertwined, Mutual Assistance (occasional fights are also normal ). What we need to do is to coordinate the relationship between the new and old systems. This coordination process is the process of solving problems using SOA.

Core concepts support heterogeneous (heterogeneous)

Do not expect every system in the enterprise to be a Java platform, do not expect every system in the enterprise to run on the window platform, do not expect the database in the enterprise to be structured ...... With the passage of time, the old version of the system depends on (the data inside is priceless, don't tell me that you can re-develop a new system, and then export the data of the old system, this is equivalent to a naive dream of re-evolution of a species in an environment in a short time !) New systems are emerging. What SOA needs to do is to ensure their "Peaceful Coexistence" on these heterogeneous (heterogeneous) systems ".

Supported changes

SOA is by no means a one-time event. With the development of enterprises, a self-defined SOA should be generated in the changes of the system environment. This time, we have integrated the new and old systems into a promising future, A company's purchase will usher in a new round of SOA process.

Several core concepts

Service: refers to each module or system. Each service can provide a function independently as much as possible.

High interoperability: similar to the concept of "Enterprise Application Integration" (EAI), it ensures that heterogeneous systems can provide services to each other.

Loose coupling: it aims to ensure the flexibility and scalability of the entire system.

The three concepts mentioned above are just like a dream for heterogeneous large-scale distributed systems (not developed at a time). How can we implement them? Maybe SOA provides us with the direction to find a solution. Please note that it is only one direction. Do not expect any specific feasible solutions from SOA. In the beginning, SOA is just a "architecture" paradigm. The specific operations still need to be summarized in practice.