Designing an XML Web Service
- Group related operations and data
into one method - Decide on:
- Arguments and return data
- Whether to use existing classes or create new ones
- Security
- Use output caching to improve performance
- Define your input and output data structures using XSD schemas
- Separate XML Web service from underlying business logic
Web Service Façade
(Architectural Patterns)
- Re-architect an existing client/server or fat client architecture into a 3 tiered application environment
- Web enable an existing client/server or fat client architecture
- Provide integration with external business partners.
- Provide integration with internal business systems.
- Insulate existing user applications from changes in APIs, servers, or vendors of data and services.
- Integrating a “silo” application — unlock an existing application so it can participate in a larger business process.
- Aggregate back-end systems so they’re exposed as one business process.
- Integrating application running on in heterogeneous environments (Linux, Solaris, AS400, etc) with applications running on Windows.
- Insulate existing user applications from changes in APIs, servers, or vendors of data and services.
- Integrating a “silo” application — unlock an existing application so it can participate in a larger business process.
- Aggregate back-end systems so they’re exposed as one business process.
- Integrating application running on in heterogeneous environments (Linux, Solaris, AS400, etc) with applications running on Windows.
No comments yet.