SOA Principles : 6. service composibility
Download as PPTX, PDF0 likes676 views
This document provides an overview of service-oriented architecture (SOA) principles including standardized service contracts, service reusability, service discoverability, loose coupling between services, and service autonomy. It discusses key SOA concepts like service composition, decomposition, and how individual services can be combined to automate business processes. Implementation requires services to be developed following standards like web services and use of frameworks to ensure reliability, security, and management of interactions between composed services. Overall, the document aims to translate SOA principles into practice by demonstrating how services can work together through composition.
SOA Principles : 6. service composibility
- 1. Principles OF SOAFrom knowledge To practice SUBMITTED BY : MOHAMED ZAKARYA
- 2. AGENDA Service orientation principles Standardized Service Contract Service Reusability Service Discoverability Service Composability Service Loose Coupling Service Abstraction Service Autonomy Service Statelessness Thanks
- 4. DAY 3 REVIEW TERM Service discoverability UDDI Service profile Service capability profile Service provider Service consumer Service loosely coupling Logic - contract coupling Consumer – contract coupling
- 6. SERVICE ORIENTATION PRINCIPLES Service Reusability Service contain agnostic logic that can be position as reusable enterprise resource. Standardized Service Contract Service in same inventory are in compliance of same design service contract standards. Service Composition Services are effective composition participants. Service Discoverability Service meta data available for discoverability and interpreted. Service Loose Coupling Contract decoupled from surrounding environment. Service Autonomy Services exercise a high level of control over their underlying runtime execution environment. Service Statelessness Services minimize resource consumption , reduce state information. Service Abstraction Contract contains only essential information , that is published to consumers.
- 8. INTRODUCTION Service Composition Services are effective composition participants. Composition considered as a form of service reuse
- 9. DECOMPOSITION The separation of concerns theory encourages us to break down a larger problem Into multiple smaller Problems (concerns)
- 10. COMPOSITION
- 11. RE-COMPOSITION The same units originally created to solve Big Problem A are recomposed (plus new other services I + J) to collectively solve a different problem
- 12. COMPOSITION EXAMPLE composition is nothing new. service-oriented composition equivalent to past composition variations
- 13. ABOUT THE PRINCIPLE Title Services are composable. Description Services are effective composition participants, regardless of the size and complexity of the composition Goals increase ROI Increase business agility much all of the goals of Service Reusability apply Provide means for a large extent of future business automation requirements to be fulfilled through
- 14. ABOUT THE PRINCIPLE Implementation requirements Runtime Hosting Environment scalable and reliable as possible . Need for dedicated, clustered servers with fail-over Services implemented as Web services Often require standardized implementations of several key WS-* extensions. Including security, reliable, messaging, activity management, and cross-service transactions.
- 15. COMPOSITION CONCEPTS AND TERMINOLOGY 1. Composition 2. Composition Instance 3. Composition Member 4. Composition Controller 5. Composition Sub-Controller 6. Composition Member Capability 7. Composition Controller Capability 8. Designated Controller 9. Service Activity 10. Point-to-Point 11. Composition Initiator
- 16. 1. COMPOSITION & COMPOSITION INSTANCE Service Composition Automation of a business process ( Static business process definition) Composition instance : what happens when an occurrence of the workflow logic is carried out by a series of service instances at runtime.
- 17. 2. COMPOSITION MEMBER & COMPOSITION CONTROLLER 1. Composition Controller Composition controller capability service is located at head of a composition hierarchy. 2. Composition Member Composition member capability service being composed by Another. Individual service capabilities that are responsible for placing services into these roles.
- 18. 3. COMPOSITION SUB CONTROLLER & DESIGNATED CONTROLLER Composition sub Controller: Composition members that compose other services Designated Controllers : Service limits to controller role only
- 19. 4. SERVICE ACTIVITIES Service activity : Mapping of an inter-service message path Representing interaction between services only Does not represent what occurs within the underlying service logic
- 20. 5. COMPOSITION INITIATOR Composition initiator : A runtime component that exists outside of this boundary is usually represented by the service consumer program responsible for invoking the composition controller in order to kick off the service composition. Program responsible for initiating the composition logic. Generally not a composition controller Service consumer : Can assume the roles of both composition initiator and composition controller
- 21. 6. POINT TO POINT DATA EXCHANGE A simple interaction between a single service and its consumer Point to point not consider a service composition. Minimum scope of a service composition two services plus the composition initiator.
- 24. ANY QUESTIONS
- 25. THANKS ENJOY SOA .. WAIT FOR NEXT MAIL: ENG.MOHAMEDZAKARYA@GMAIL.COM
Editor's Notes
- #3: 6 main parts of presentation !
- #10: The separation of concerns theory encourages us to break down a larger problem into multiple smaller problems
- #15: hosting runtime environments need to be as scalable and reliable as possible
- #16: hosting runtime environments need to be as scalable and reliable as possible
- #17: hosting runtime environments need to be as scalable and reliable as possible
- #18: Primitive composition : Implemented during the early stages of a service inventory when few actual composable services are available Complex service compositions: Automate larger and more demanding business processes
- #19: Designated Controllers : Task service with just one capability used to kick off the automation of a business process which will involve the composition of multiple other services.
- #20: Activity sequence ( the numbers in arrows)
- #21: Activity sequence ( the numbers in arrows)
- #22: consumer program that interacts with a service that does not invoke any other services is an example of the point-to-point model.
- #23: خلص ورقة في الجوازات المخالفات المروية تفويض سيارة فيزا