Basic features of the SOA family

The previous blog has introduced the basic concepts of SOA, so we should have a basic understanding of SOA as a programming concept, and today we continue to introduce some of the basic features of SOA to help you understand SOA more deeply.

For each set of mature architectures will have his own characteristics and ideas, below we basically from five aspects to introduce the characteristics of SOA.

Service autonomy

The principle of service autonomy requires that a single service be as independent and self-contained as possible in the underlying logical control, and that the service does not rely on clients or other services that access it. Services can be deployed independently and implement version policies and security policies.

Reliance on open standards

One of the goals of SOA is to enable services developed by different vendors to interoperate with each other so that it relies on an open standard that is universally accepted by different vendors. SOA uses message-based communication, from the perspective of message exchange is to require the message itself standardization, in this method soap ( Simple Object Access Protocol ) messages to the content of the message to provide a consistent representation. In addition, when SOA is truly used for enterprise-class applications, additional factors such as message security, reliable transmission, transactional support, and so on, need to be considered. To achieve a truly cross-platform operation, the interoperability of these features requires an open standard. In this regard, some major IT vendors such as Microsoft, IBM and BEA, such as the United International organizations such as: World Trade, OASIS, WS-1, etc., have made great contributions to the designation of standards and specifications, these standards and specifications are defined in the Web Service specification.

Support Cross-platform

Being able to communicate on different platforms is the most important motivation for SOA to occur. It is the open standards that SOA employs that enable cross-platform implementations. The best cross-platform benefit is the integration of heterogeneous systems that enable Java applications to invoke the service interfaces exposed by the. NET Platform. In addition, the use of standard services to deliver a logical package, to achieve the reuse of legacy applications, but also provides enterprises with a cost-saving shortcut.

Combination and Reuse

Different services have different granularity depending on the size of the provided functionality. We can turn services that provide the least granular functionality into atomic services, and multiple atomic services can be orchestrated into a new aggregation service through a reasonable combination. The reuse of functionality is a constant theme of my software design, and SOA encourages the creation of services that are highly reusable. The combination of services also facilitates reuse of services on the other. To improve the reusability of the service, SOA even emphasizes the creation of a scenario-independent service, so that the same service is used in the solution for different scenarios.

Loose coupling

SOA implements client-to-service invocation through contracts, and both parties can guarantee normal interactions by simply matching the contract. Contract-based service communication, and further promote the autonomy of services, as long as the contract does not change, the implementation of the service itself can be free to change, so this coupling degree is very low.

So much for the basic nature of SOA, the following blog will continue to update the more in-depth content of SOA, please continue to pay attention!

These are the basic features of the SOA family, and more about topic.alibabacloud.com (www.php.cn)!

