Document directory
- New SOA business language new system architecture-Reference Model and important concepts
- IBM
- Microsoft
- Bea
SOA new business language new system architecture-Reference Model and important concepts SOA reference model is a framework that enables each project to have a basis for compliance, so as to promote consistency and best practices, and standardization. The reference model is not limited by the current IT status, but should be targeted at a well-thought-out vision. It can be said that it guides all future development work and serves as a reference for achieving this goal. Generally, a two-or three-year plan is suitable for service-oriented transformation. It will not be too long-term or illusory. Therefore, the reference model provides a communication goal vision method to help different departments and IT personnel with different roles gradually converge towards this goal. The SOA reference model guides all SOA implementation projects to develop enterprise-level services and SOA infrastructure standards in a centralized manner, so as to benefit enterprises as soon as possible. In other words, the focus of Reference Model planning is to develop a feasible road map specific to the needs of an enterprise to bridge the gap between the current and vision objectives; evaluate existing systems and technologies used for development, deployment, management, and monitoring, define the target State vision, and target reference model. The SOA reference model is a blueprint for guiding SOA success. Its functions include:
- Promote close cooperation between it and business: refer to the formulation of models, and analyze the positive impact of SOA solutions on these driving forces based on business drive and it goals, then, we will determine the implementation architecture, relevant specifications and road map for the evolution from the current IT status to the vision architecture. Therefore, the reference model provides traceability between the business and IT objectives and the implementation architecture, which is an important medium for communication between the business and IT, it is the foundation for enterprises to implement business flexibility, manageability, and change planning.
- Assists enterprises in the cultural migration to reuse, team collaboration, and resource sharing: refer to the model to establish the best practices for SOA Architecture Standards and Technical deployment, for future SOA implementation projects, establish architecture compliance metrics and metrics.
We can roughly divide the reference model into two parts:Establish a set of common terms and practices for services, including:
- Formal Definition of a service-for example, a service must be composed of contract, interface, and implementation
- Service classification (core business function services, data services, presentation services, etc.), as well as design principles and suggestions for various services
- Interface standards (JMS, RMI, HTTP, etc.), recommended interface styles (for example, use coarse-grained and asynchronous service call modes as much as possible), and reliability requirements
- WS-* standards to be followed
- Security Policy
- Service version control policy
- Specifications for service and data model adoption
- Service lifecycle Definition
Specifications related to service infrastructure, such as Enterprise Service Bus (ESB), business process management (BPM), registry, and repository, including:
- What deployment configurations must be supported?
- What capabilities are required?
- Responsibilities of various components
- The coupling relationship and principles between components should be avoided, for example, displaying services and business process services cannot directly call data services, but must pass through core business services; in other words, data Services cannot be directly coupled with presentation services and business process services.
- Various components should support those technologies and standards (such as SCA, SDO ...)
- What security concerns should be considered and how to manage permissions?
- Products to be used
Ibm soa Foundation Reference Model Microsoft BEA: 4 + 1 views adjusted for the SOA reference model
