Organizing service layers:
1. Applicaiton Service layer: ERP, mainframe, Custom application, RDBMS, WS
2. Virtual service: decouple application services from consumers, Service description and end point virtualisation
3. Business service: Service provide common schema and encapsulated business logic.Functional, Entity, task based
4. Business processes:
5. UI layer
Service design considerations:
Granularity with performance
Service consumption
Security
Management: SLA
Support
Change Management
Validation
What you need to ensure while designing service:
Service granularity: performance is key here when you are breaking almost everything into pieces
Service re-use
Service Lifecycle
Service Security
Service Management
Design a service:
Schema definitions
WSDL definitions
WS-Policy definitions
Schema guidelines
Naming standard
Namespace considerations
Do not use default name space
Prefer qualified namespaces for elements
unqualified name spaces for attributes
http://<domain, com/in/blah blah..>/<sub-domain>/<namespace-type>/<subject_area>
Any simple element should be defined as global type element, specifically those which are used as input/output parameters of any service. And same can be used to define any schema.
1. Applicaiton Service layer: ERP, mainframe, Custom application, RDBMS, WS
2. Virtual service: decouple application services from consumers, Service description and end point virtualisation
3. Business service: Service provide common schema and encapsulated business logic.Functional, Entity, task based
4. Business processes:
5. UI layer
Service design considerations:
Granularity with performance
Service consumption
Security
Management: SLA
Support
Change Management
Validation
What you need to ensure while designing service:
Service granularity: performance is key here when you are breaking almost everything into pieces
Service re-use
Service Lifecycle
Service Security
Service Management
Design a service:
Schema definitions
WSDL definitions
WS-Policy definitions
Schema guidelines
Naming standard
Namespace considerations
Do not use default name space
Prefer qualified namespaces for elements
unqualified name spaces for attributes
http://<domain, com/in/blah blah..>/<sub-domain>/<namespace-type>/<subject_area>
Any simple element should be defined as global type element, specifically those which are used as input/output parameters of any service. And same can be used to define any schema.
No comments:
Post a Comment