Service-Oriented Architecture (Service-Oriented Architecture, SOA) is a component model. Different functional units of the application (called services) through well-defined interfaces and contracts between these services together; UI is defined in a neutral manner, it should be independent of implementation services of hardware platforms, operating systems and programming languages; to build such a system in a variety of services in a uniform and common way to interact.
Web service platform is a standard that defines how an application interoperability on the Web. You can use any language you like, you like to write on any platform Web service, as long as we can query and access to these services through Web service standards. Web service is a technical specification, SOA design principles. Essentially, SOA is an architectural pattern, while the web service is the use of a set of service standards implementation. Web service is one way to achieve SOA. The benefits of using web service SOA is real: you can achieve a neutral platform to get the service, for better versatility. Web Services is the immediate goal of the assembly, as well as automatic loosely coupled integration.
Why use SOA? The traditional architecture, the package is being prepared for independent (self-contained) software, that together in a complete package will feature a number of applications. Code to achieve the integration of application functionality and function code itself is usually mixed together. In this way we will design software called "single application." Closely related to this is that part of the code will change the code to use the code has a significant impact, which will result in system complexity and increase the cost of maintaining the system. But also the re-use the application functions become more difficult, because these features are not playing for re-use package. Disadvantages: code redundancy, can not be reused, tightly coupled, high cost.
SOA intended single application functionally separated from each other, so that these functions may be used alone as a single application functionality or "components." These components can be used to create a variety of other in-house applications, or if necessary, publicly available to partners for use in applications partners. SOA advantages: code reuse, loose coupling, platform-independent, language-independent.
SOA architecture has three roles: service provider: publish their services, and to respond to service requests. Service registry: Registration has released the web service, classify, and provide search services. Service requester: Using Service Center to find the services they need, and then use the service.
SOA of three operations: publishing operation: In order to make the service accessible to the need to publish service descriptions service users can find it. Find operation: service requester location-based services by querying a service registry to find meet their standards of service. Bind operation: After retrieving the service description, service users continue to call the service based on the information in the service description.
Reproduced in: https: //www.cnblogs.com/chrran/p/11082272.html