Introduction and practice of Web Service

This section briefly introduces SOA and my personal understanding of WebService. Some problems that need to be paid attention to during the implementation of a specific project.
References:
(1) http://webservices.xml.com/pub/a/ws/2003/09/30/soa.html
(2) ms-help: // MS. VSCC.2003/MS. MSDNQTR.2003FEB. 2052/cpguide/html/cpconanatomyofsoapwebservicelifetime.htm
(3) ms-help: // MS. VSCC.2003/MS. MSDNQTR.2003FEB. 2052/cpguide/html/cpconcustomizingsoapinaspnetwebserviceswebserviceclients.htm


"When talking about the world's major events, we must combine them for a long time." (The Romance of the Three Kingdoms)-is the same for the software industry?

Currently, the software industry has a variety of technical platforms and architecture. However, since different platforms focus on different aspects and have different characteristics, it is difficult to communicate between platforms, this forms an isolated information islands. how can we link these isolated information islands .? The industry has put forward many solutions. A well-known solution is Serviced-Oriented (service-Oriented). What is service-Oriented? This is its definition: "SOA is an elastic tural style whose goal is to achieve loose coupling among interacting software agents. A service is a unit of work done by a service provider to achieve desired end results for a service consumer. both provider and consumer are roles played by software agents on behalf of their owners. "(1 ). service-oriented is a collection of services. each service can communicate with each other (including simple data transfer and multiple services participate in one activity). It provides some external interfaces for each system to integrate various systems. the industry also has some corresponding architecture, such as: DCOM. CORBA. j2EE. however, cross-system integration cannot be fully implemented. I personally think the reasons are as follows:
1. the interface definition language cannot be received by different systems. whether it is DCOM. both COBRA and J2EE have their own interface definition languages (both binary ). they cannot be accepted by other systems. once the interface is set, it is difficult to change. user requirements are constantly changing.
2. the binary network protocol is used for data communication. It is difficult to cross the firewall and the protocols used by them are not widely accepted. This is especially important for Internet application.