Table of contentsWeb Service Architectures
The Point
Outline
Definition
Basic Architecture
SOAP Messages
SOAP Status
REST Background
REST Status
SOA Background
SOA Implications
Architecture Issues
Composable Services
Service Components
Common Formats
XML Formats
Service Contracts
Interface vs. Implementation
Design Issues
Communications Costs
Structuring Costs
Schema Compatibility
Schema Recommendations
Extensibility Issues
Adding Operations
Adding Data
Other Changes
Schema Versioning
SOAP Changes
Indigo
WS-Addressing
WS-Security
WS-Reliability
WS-AtomicTransactions
More WS-*
XOP / MTOM
SOAP vs. REST
EJBs vs. Servlets
Future of REST
Road to SOA
Take a Bus?
SOA Steps 1
SOA Steps 2
Questions
|
Author: Dennis M. Sosnoski
E-mail: enquiry@sosnoski.com
Homepage: http://www.sosnoski.com/
Further information:
Presentation delivered before the New Zealand
chapter of the WWISA in Wellington, New Zealand, 13 February 2006. This
material gives an overview of the practical issues involved in building toward a
Service Oriented Architecture (SOA).
Web Services are the building blocks of modern Service Oriented Architectures.
When used properly, they offer excellent interoperability for an ever-increasing
range of enterprise requirements. But before you can achieve the benefits you
have to navigate the hazards, starting with basic choices such as REST vs. SOAP
and going on to issues of interface structuring, XML schema compatibility and
service evolution over time. These practical concerns are often overlooked in
the high-level discussions of service governance and other business issues, but
they play a key role in the long-term success or failure of a SOA.
An earlier version of the same material was presented at
Javapolis 2005.
Also see: Java Web services, Part 1: The year ahead in Java Web services
|
