New SOA business language new system architecture-the purpose, significance and value of SOA

Document directory

• Service-oriented value (from the book of WCF programming)

For the purpose of SOA, IBM says:The fundamental purpose of SOA is business agility. How to understand agility is understood from two aspects: first, it responds to this change in an appropriate period of time after the business changes are proposed; second, changes made by it can properly reflect business needs. Microsoft said:The specified tural concepts associated with SOA enable loose coupling. Loose coupling is the fundamental principle behind SOA, enabling us to summarize up the benefit of SOA in a single word: Agility. Wang wenjing said:(Chairman of yonyou software) for today's enterprises, rapid response and rapid changes are becoming a key factor for success, "flexibility" is increasingly becoming the most important thing for CIOs and enterprise users to get from IT systems. Linking internal and external processes, personnel, and information of an enterprise in real time to respond to changes flexibly and quickly is a key goal of Enterprise Informatization. SOA (Service Oriented Architecture) IT architecture and methods that help enterprises achieve this goal. Flexibility, or agility and agility, has become the core objective and fundamental driving force of SOA. This is determined by the current wave of globalization and the nature of business competition.As Thomas ERL stated in SOA concepts, technologies and design: The minimum effort is used to obtain the greatest benefit. This is the requirement of competitive businesses for the company's strategic objectives. Inefficient organizations that are constantly wasting resources will lag behind. The Organization's business automation method is the fundamental factor determining its operational efficiency, and thus a reward for its daring to take risks. This is SOA. . Service-oriented Automatic business logic can protect existing investments, help intelligently express businesses, and thus express internal auto agility. When compared with Web SOA It provides an important potential benefit to change the technology and development prospects of the Organization.In addition to flexibility, SOA can also bring the following benefits to enterprises: 

1. Improved architecture and solutions. 2. Create a standard XML data representation. 3. Focus on communication infrastructure investment. 4. Improved Integration (and internal interoperability ). 5. Internal reuse. 6. protect existing investments and legacy assets. 7. "optimal supply" can be replaced.

 

Service-oriented value (from the book of WCF programming)

Because the interaction between the client and the service is based on industry standards, this industry standard includes the methods to ensure call security, spread the transaction stream, and manage reliability. We can also use the existing implementation of these public basic functions. This ensures the maintainability of the application, because the application has nothing to do with accuracy. Even if the common basic functions evolve, the application will not be affected. Service-oriented applications are robust because developers can use available, verified, and tested public basic functions. At the same time, it also improves the efficiency of developers, because they can spend more time to implement functional features, rather than these basic public functions. The real value of service-oriented is that developers are allowed to extract the implementation of common basic functions from the code and pay more attention to the business logic and required features.

Service orientation also includes many popular values, such as cross-technology interoperability, which reflects the core value. Although we can achieve interoperability without the help of services, it is not until the birth of service-oriented that we can apply it to practice. The difference between the two lies in that the latter can provide developers with interoperability through existing public basic functions. When writing a service, you usually do not need to consider the platform on which the client runs, because the service-oriented architecture completely achieves seamless interoperability. Service-oriented applications not only provide interoperability, but also allow the system to span boundaries. One of the boundary is the boundary between technology and platform. Crossing such boundary fully reflects interoperability. However, boundaries may still exist between clients and services, such as security and trust boundaries, Region boundaries, organization boundaries, time zone boundaries, transaction boundaries, and even business model boundaries. Seamlessly crossing these boundaries is possible because of message-based interaction standards. For example, the standard to ensure message security and the standard to establish secure interaction between the client and the service, even if the interaction is in a domain (or site) that does not have a direct trust relationship. Transaction Standards allow the Transaction Manager of the client to pass the transaction to the transaction manager of the server, and let the Service participate in the transaction, even if the two transaction managers never directly register each other's transactions.