soa principles : 6. service composibility
TRANSCRIPT
Principles OF
SOA From knowledge To practice
SUBMITTED BY : MOHAMED ZAKARYA
AGENDA
Service orientation principles
Standardized Service Contract Service Reusability Service Discoverability Service Composability Service Loose Coupling Service Abstraction Service Autonomy Service Statelessness Thanks
PART 1
INTRODUCTION
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
SERVICE ORIENTATION PRINCIPLES
Standardized Service
Contract
ServiceReusability
ServiceComposability
ServiceAutonomy
Service Loose
Coupling
Service Statelessness
ServiceAbstraction
ServiceDiscoverability
SERVICE ORIENTATION PRINCIPLES
Service ReusabilityService contain agnostic logic that can be position as reusable enterprise resource.
Standardized Service ContractService in same inventory are in compliance of same design service contract standards.
Service CompositionServices are effective composition participants.
Service DiscoverabilityService meta data available for discoverability and interpreted.
Service Loose CouplingContract decoupled from surrounding environment.
Service AutonomyServices exercise a high level of control over their underlying runtime execution environment.
Service StatelessnessServices minimize resource consumption , reduce state information.
Service AbstractionContract contains only essential information , that is published to consumers.
PART 1
SERVICE
COMPOSITIOABILITY
INTRODUCTION
Service CompositionServices are effective composition participants.
Composition considered as a form of service reuse
DECOMPOSITION
The separation of concerns theory encourages us to
break downa larger problem
Into multiple smaller Problems(concerns)
COMPOSITION
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
COMPOSITION EXAMPLE
composition is nothing new.service-oriented composition
equivalent to past composition variations
ABOUT THE PRINCIPLE
TitleServices are composable.
DescriptionServices are effective composition participants, regardless of the size and complexity of the composition
Goals
increase ROIIncrease
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
ABOUT THE PRINCIPLE
Implementation requirements
Runtime Hosting Environmentscalable 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.
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
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 logicis carried out by a series of service instances at runtime.
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 byAnother.
Individual service capabilities thatare responsible for placing services into these roles.
3. COMPOSITION SUB CONTROLLER & DESIGNATED CONTROLLER
Composition sub Controller:
Composition members that compose other services
Designated Controllers :
Service limits to controller role only
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
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
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.
SERVICE COMPOSABILITY DEMO
التسليم الي اإلستالم من البريدية المواد نقل عمليةللعميل
إستالم من
العميلالمعالجة
الترحيل
التوزيعإرسال رسالة المكتب للعميل نفس توزيع
التسليمالنهائي
REFERENCES
http://www.soaschool.com/
http://serviceorientation.com/index.php/soaglossary/index
http://soapatterns.org/
http://www.servicetechmag.com/
http://www.soaschool.com/certifications
http://www.servicetechbooks.com/
ANY QUESTIONS
