New SOA business language New System Architecture -- building SOA

Document directory

• New SOA business language New System Architecture -- building SOA
• IBM
• Microsoft
• SOA concept, technology and design

SOA new business language new system architecture-building SOA for enterprise businesses, the biggest advantage of the Service-Oriented Architecture (SOA) is flexible response capabilities. Enterprises are often affected by various changes: market, supply chain, strategic processes, rules, etc. SOA can establish a flexible environment to respond to various changes reliably. The reason is that SOA restructured automated functions in a reusable manner so that new or corrected processes can be quickly configured. However, it is not enough to rely solely on one architecture to achieve agility. Agility comes from various aspects that provide agile processes. You must have a deep understanding of the business to develop, reconstruct, or establish a proper service. Due to standardized best practices, deep communication and data protocols, and industry "Openness", SOA almost experienced a perfect storm of agility. The efforts of enterprise integration and the development of object-oriented theories have gradually formed the best practices. Due to the development of the Internet, the Management Technology (plumbing) has become a must for in-depth understanding and general integration. The customer's needs, open source and open information movement contribute to the open development. Why is it almost a perfect storm? As with the previous technology, SOA is only an enabling technology. If you do not have a deep understanding of the current business process or an overall understanding of the process changes, you cannot correctly select components and form perfect agility. SOA is not just about how to do it. What should we start with in real business planning. Simply put, if you do not know what to do, even if you know how to do it, what to do is irrelevant.

Use blueprints to achieve "intermediate encounter"

What can guide these new architecture methods and the application of underlying technologies? What can prevent SOA practitioners from simply organizing and failing to achieve the true agility and business goals of SOA? What can ensure the well-organized "Soa" architecture can bring considerable benefits? In the SOA field, the importance of governance has been discussed a lot, but this is still a question about how to do it, not what to do. For example, governance during design should support Component Reuse, which is an important aspect of SOA. If it cannot be reused, why do we have to spend money on this reusable development? However, there is little discussion about the process of deciding which parts to reuse. Moreover, the prerequisite for success should be a model that can guide the selection or creation of components that truly achieve agility so that components can support new or higher-level business processes. There are also many discussions about adopting SOA in the top-down or bottom-up mode. Both methods have different advantages and disadvantages. A top-down approach can make you "feel good", because it is based on full analysis and investigation, but it can easily lead to unrestricted descriptions or standards, that is, "weak analysis" means that the plan cannot catch up with demands and technical updates. The bottom-up approach facilitates quick start, usually to pursue new technologies and has the advantages of the "organic" approach. However, this method often leads to reusable components or unorganized services. Although it complies with some service-oriented rules, it cannot provide true agility or reproduce business service consistency. There is also a "meet in the middle" strategy that can combine the advantages of both. It is the easiest way to control and plan business goals and reorganize them, as well as to support these goals. However, the "best planning" can also be used in bottom-up methods, that is, starting first, restructuring and learning experience in the process, it also supports fine-grained adjustment based on changing priorities, requirements, and technologies. Because it supports parallel development, the "encounter in the middle" method usually has the advantage of time, while the top-down method usually represents different organizations and rules. But this is exactly the problem that needs to be solved. Two teams working to "encounter in the middle" need to know exactly how they will connect. This is not a problem that can be easily solved. A comprehensive hierarchical model (generally called a blueprint) that represents the current and expected status can effectively support the "Intermediate encounter" method. This method requires clear tracing from the top-down method, and the blueprint can provide this. With such a blueprint, the "ambitious goal" will be maximized, and parallel development can be carried out based on infrastructure and process needs. This is the advice provided by SOA practitioners to build a proof-of-concept that has good visibility and requires a simple view to stay focused. Using this method in the blueprint of interactive development enables you to explore tracing from the business goals to the infrastructure that helps achieve the goals from top to bottom. Based on sufficient high-level modeling and definition, the key process of early development should be determined. However, it is necessary to enter the development process as early as possible to accumulate experience for the next step, so as to be knowledgeable and confident. Because of the good traceability of the blueprint, you can view the requirements met by the current implementation or proof of view (POC. It can also be used to capture changes in every step of the SOA-based enterprise process and provide appropriate components for maximum agility. A blueprint is a common language that defines the point of contact between the top business structure and the underlying system architecture. The blueprint ensures that the plan can truly "encounter in the middle ". In essence, the blueprint is the "Architecture copy" of each enterprise, and because it is actually started by software tools, it is more appropriate to call it a digital model. In the blueprint, governance becomes a control and communication architecture that implements this "copy. The scheduler can provide progress and resources for gap analysis between the "as is" model in the blueprint and the "to be" model ). Because of the traceability between layers in the blueprint, you can determine the business processes to be changed by optimizing the business objectives, and then determine the underlying automatic control and components based on the business processes, finally, determine the infrastructure to be changed. With the blueprint, it is easy to optimize the project based on the business scope, ROI, available resources, or other non-direct architecture and technology-related factors. In this way, the plan can be executed in parallel and all components can be provided according to the progress to achieve the consistency between it and business goals. Source: SOA http://soa.csdn.net/page/ea2ccde0-36fd-40e7-968a-bd557faa9c32 for agile enterprise change ibmibm found and pointed out five entry points that can help customers more easily implement an SOA project. These entry points include: people, process, information-centric approach, and system connectivity) and the ability to reuse existing assets (creating and reusing services ).

• The personnel-centered SOA entry point can provide enterprises with a comprehensive view of information and interaction in business processes to improve personnel productivity. Hanover Insurance Company of the United States has improved its business processing speed by 75% by deploying an SOA portal.
• A process-centric SOA entry point is a rapid deployment of innovative business models with reuse and optimization processes. Wachovia achieved 80% automation through a single process and further innovated customer services.
• Information-centric SOA entry point provides reliable information services using embedded (in-line) or in-context methods to improve business insight and reduce risks. With this method, the recruitment efficiency of Volkswagen has increased by 20%.
• The SOA connection entry point uses the connection as the basis to support business-centric SOA. It provides services through a new business channel with any-to-Any connectivity to ensure a secure and consistent user experience. At the same time, it can save 2 to 4 times the cost compared with custom integration or FTP.
• The entry point of SOA creation and reuse services allows you to easily reuse SOA management. Reuse can reduce costs, reduce cycles, expand core applications, and reuse existing applications only costs 1/5 of the fee required to rewrite new applications.

Microsoftmicrosoft advocates a-"Middle out" approach which combines both top-down and bottom-up methodologies. in this approach, SOA efforts are driven by strategic vision and business need, and are met through incremental, iterative SOA projects that are designed to deliver on business goals one business need at a time. microsoft has been using this technique to assist MERs with their SOA initiatives since. NET framework was first released in 1999. SOA concept, technology and design

• SOA delivery strategy: top-down, bottom-up, agile
• Service-oriented analysis: Service Modeling
• Service-oriented design: WSDL and soap
• Service-oriented design: Guiding Principles of SOA combination
• Service-oriented design: Service Design
• Service-oriented design: Business Process Design
• WS-* Extension