As I mentioned in a post here last week, I had the honor of keynoting the SOA Symposium that took place earlier this month in Amsterdam, which brought together more than 500 attendees representing the cream of organizations from across western Europe. The purpose of my keynote was to help launch Thomas Erl's latest work, SOA Design Patterns, which documents design patterns for 85 essential services that make up most SOA efforts.
Thomas Erl and his colleagues have been working on identifying and sculpting SOA patterns since 2004. If we're going to do SOA, we need to do it right, and borrow heavily from best practices identified and laid out by industry practitioners. The ability to develop services that can seamlessly integrate with each other will save a lot of resources and time. In addition, following design patterns help alleviate pressure to align services with business processes.
Here is a brief summary of the patterns Thomas and his colleagues have identified:
Inventory Design Patterns: Foundational Design Patterns; Logical Inventory Layer Patterns; Inventory Centralization Patterns; Inventory Implementation Patterns; Inventory Governance Patterns.
Service Design Patterns: Foundational Service Patterns; Service Implementation Patterns; Service Contract Design Patterns; Legacy Encapsulation Patterns; Service Governance Patterns.
Composition Design Patterns: Message Processing Patterns; Composition Implementation Patterns; Service Interaction Security Patterns; Transformation Patterns.
____________________________________________________________________
And lets not forget our dusty but still very relevant CORBA design patterns. ;-)
Robert
soaprobe.blogspot.com