Web Service is a collection of technologies that are most suitable for implementing SOA, in fact, the recent popularity of SOA is largely due to the maturity of web service standards and the popularity of applications, which provides the foundation for the wide implementation of SOA architecture. Let's take a look at how various protocols in Web service work with each other to meet the characteristics required by SOA:
Independent functional entities: by searching the UDDI directory, We can dynamically change the provider of a service without affecting the client applications.ProgramConfiguration. All accesses are implemented through soap. As long as the WSDL interface is well encapsulated, the external client cannot directly access the data on the server.
Low-frequency access to large data volumes: Using WSDL and literal-based SOAP requests, we can implement interfaces that can receive large amounts of data at one time. It is important to note that SOAP requests are divided into text and Remote Call (RPC) methods. As mentioned above, SOAP requests using remote call methods do not meet this requirement. Unfortunately, most existing SOAP requests still use the Remote Call (RPC) method. On some platforms, such as earlier versions of IBM WebSphere, no text soap support is provided.
Text-based message transmission: All Web Services communicate through soap, while soap is based on XML. Different versions can be identified and differentiated using different DTD or XML schema. Therefore, we only need to provide different processing for different versions to easily achieve version control goals.