SOA definition
First of all, what is a service? Service is a repeatable logical expression of business tasks. It is necessary to emphasize here that we talk about part of the business process, not part of software or IT. After technology implementation, the term "service" is applied to software resources that use external normative (which can be found). This service specification allows service users to search, bind, and calls. The service provider is implemented for service specifications and delivers service quality requirements to service users. The service will be controlled by the declarative policy, so the architectural style that can be dynamically reconfigured.
Second, what is the service? Based on our service definition, the service is a way to integrate business as a set of services. We are still not technical; we talk about a new way to look at business and its operational way. What is SOA? SOA is a service-oriented architecture style. SOA is an enterprise-level IT architecture for associating resources as needed. These resources are expressed as a service consistent with business, which can participate in and include to value network, enterprise or business line to meet business needs.
Finally, what is the combination application? It is a set of integrated services. The combined application is an actual operation of the actual operation to support the functions of the business. The main structured elements of the SOA application are services, not subsystems, systems, or components.
SOA is not a new concept; Common Object Request Broker Architecture (Corba) and Distributed Component Object Model have long provided similar features. However, these solutions for service positioning are subject to some problems, such as tight coupling scenes and ownership design and implementation.
Service and components
What is a service? Services is just some application functions that are published as components of business processes. Like the same parts, it provides an independent build module that together represents the business application environment. The service is clearly defined, independent work units, does not rely on context or other services, and execute the final result of the service provider to complete the service client. Providers and customers are responsible by representing their own software components. Using SOA, all business tasks or processes can be designed and used as services used on the Internet (or any other network).
The software component architecture has been formed as standard design examples in many areas developed by application development. It is achieved from the development of object-oriented technology, by providing high-level extraction and encapsulating low-level objects into reused technical components (adjustment to be suitable for business operations and can be repeatedly designed, developed, and refined) .
In order to explain the relationship between components and services, through how to be "executable code units", it provides a physical black box package for related services. It can also be accessed by the consistent, published interface that contains interaction standards. Services. Components must be able to connect to other components (via communication interface) to form large groups "(Component-based development in the enterprise system: Application Selection Perspective - See Refiguring) You can get inspiration.
Attachment: instance
SOA service-oriented business conversion in the best practices in the retail industry
