Document directory
SOA! = Web service many place equal signs on Web Services and SOA and regard it as the only choice for implementing SOA. Jason Bloomberg does not agree to this. Recently, he gave his opinion on "breaking up the marriage between SOA and Web Services. "We think SOA and Web services are the same thing and may be the most annoying misunderstanding in the market around the service-oriented Architecture (SOA. Unfortunately, this chaotic view is very popular and has an impact on architects and developers. Consultants and vendors are no exception ." We must clearly distinguish between SOA and Web Service Specifications-sometimes, the two are confused: SOA is the architecture, while web service specifications define an SOA-supported interoperability platform. SOA is not brand new. In practice, some aspects of SOA have been used for a long time. For example, for "loose coupling": many years ago, enterprises used reliable message transmission technology to integrate applications, that is, to decouple them. Do not misunderstand me. There are also new concepts in SOA, such as those created by combining the concepts of SOA, that is, they are gradually generated. Web service specifications enable effective cross-platform technology. That is to say, the corresponding norms basically do not invent new concepts, but define these concepts and how they work in a heterogeneous environment. The result is that interoperability is broken out, and SOA becomes a reality. We are aware that today is a basic fact of foresight: Although using web services alone can reduce the cost of integration, only turning to SOA can reduce the long-term cost of business changes for organizations. In other words, the Web Service gives you a ticket to the dance, but you still need to learn to dance. As a matter of fact, when many IT product manufacturers see the gold in the SOA well, the Web Service floats began to fall. These vendors began to shoot web service interfaces on their products, claiming that they are service-oriented. This approach is just as valuable as applying lipsticks to pigs. In fact, the Web service interfaces of applications or databases, or even Web Service adapters on the proprietary message middleware, are not SOA. Now is the time to better separate these concepts and let SOA evolve at a higher abstraction level. But not everyone agrees that web services should be separated from SOA. For example, Frank Cohen agrees that they are different terms, but he also thinks that they are closely related: SOA and Web services are very useful visions, it helps us move from the current XML, platform, application and service (I call it xpad operations) to the future. Over the years, it has always wanted to achieve this type of interoperability, reuse, and governance, including its efforts in this area, such as CORBA, opendoc, DCE, Client/Server, web 1, Web 2.0, and Enterprise Web 2.0. All those efforts can provide a component architecture in which software can be reused to accelerate the market opportunities for enterprises, and then provide better consumer opinions for enterprises. SOA retains the concept of WS components, focuses on combined applications used for business workflows, and orchestrates governance, business problems, troubleshooting, and Quality of Service (QoS) for static proxy endpoints) instead, the idea of discovering services is discarded. Address: http://www.infoq.com/cn/news/2007/07/soa-ws-relation
