Categories
AntiPatterns
Architecture
Best Practices
Career Advice
Data Access Patterns
Design Paradigms
Enterprise Application Patterns
Fundamentals
Humor
Leadership
Musings
Object-Oriented Programming
Service Oriented Architecture
Software Architecture
Software Development Practices
Windows Communication Foundation
|
7/28/2008 12:00:00 AM
Rob Daigneau
SOAP has become the De facto standard for more complex service designs where there is a need for applications integration and collaboration. However, our use of WSDL and the wide-spread adoption of the Document-Literal-Wrapped pattern by SOAP toolkits have led to a proliferation of services that look remarkably like procedures and synchronous RPCs. That’s too bad, because SOAP is, at its core, a foundation for enabling one-way message exchanges. In order to more fully realize the benefits of SOA, we must reconsider the patterns we use when we design our services. Join us in this session to explore how we might evolve from a procedural orientation to a messaging orientation when using SOAP.
|