Service Oriented design Principals
Following are key principals that would bring interoperability, vendor diversification options, increased ROI, increased Organizational Agility and going forward reduce IT costs.
Standardized service Contracts:
Services within the same service inventory are in compliance with the same contract design standards. This increases inherent interoperability and as it brings natural compatibility between data models in service contracts and also reduces need for transformation in middleware.
Service loose coupling
: By consistently fostering reduced coupling within and between services we are working towards a state where service contracts increase independence from implementation and services are increasingly independent from each other. Increase interoperability by making individual services less dependent on each other and therefore more open to sharing data with different service consumers
Service abstraction
: Service contracts only contain essential information and information about services is limited to what is published in service contracts. The primary role of this principal is to keep the quality and detail of contract contents concise and balanced and prevent unnecessary access to additional service details. In GAT solution ESB will provide service abstraction
Service reusability
: Services contain and express agnostic logic and can be positioned as reusable enterprise resources
Service Autonomy
: Services exercise a high level of control over their underlying runtime execution environment. Services have a contract that expresses a well defined functional boundary that should not overlap with other services
Service Statelessness
: Services minimize resource consumption by deferring the management of state information when necessary
*source Thomas Erl
No comments:
Post a Comment