|
Introduction to SOA Types & Design Patterns
|
|
Read the article "Introducing SOA Design Patterns" from the
June 2008 SOA World Magazine (High-Res PDF).
|
|
|
PLEASE NOTE
The content on this page is from the first draft of the manuscript for the upcoming book "SOA Design Patterns" by Thomas Erl. This version of the manuscript was authored in September, 2007. Since then, the manuscript has undergone significant content and structural changes as a result of an industry-wide review in which hundreds of SOA practitioners participated in addition to SOA vendors and experts from the design patterns community.
You are welcome to use the information on this page for research purposes, but you should assume that most of it will change in the final release of the "SOA Design Patterns" book.
Note also, that as a result of an industry-wide call for participation from December 2007 to February 2008, over 30 new design patterns have been contributed to this book. As they become finalized and are incorporated by the author, concise descriptions will be published on this site, and full descriptions with examples will be made available in the final, printed book.
Due to the volume of new content and changes, the release of the "SOA Design Patterns" book has been postponed to October, 2008. To learn more about the book, visit www.soapatterns.com. To be notified of updates to this site, use the notification form.
|
|
|
Chapter 8: Service Design Patterns
|
Home >
Chapter 8 Overview
|
Introduction
There are many design and runtime scenarios that services can find themselves in. The fundamental nature of service capabilities to be naturally composable into creative configurations makes the evolutionary path of the services within a given inventory unpredictable.
Note that although these patterns have been placed into a chapter that is separate from the collection of architectural design patterns Chapter 6, some are still architectural in nature. They are located here specifically because their application relates to or supports the strategic use of service contracts.
The list below provides an overview of all the design patterns in this chapter.
|
|
|
Concurrent Contracts
How can a service facilitate multi-consumer coupling requirements and abstraction concerns at the same time?
|
|
Contract Centralization
How can direct consumer-to-implementation coupling be avoided?
|
|
Contract Denormalization
How can an agnostic service contract be designed to facilitate a range of consumer programs?
|
|
Decomposed Capability
How can a service be designed to minimize the chances of capability logic deconstruction?
|
|
Decoupled Contract
How can a service express its capabilities independently of its implementation?
|
|
Distributed Capability
How can a service preserve its functional context while also fulfilling special capability processing requirements?
|
|
Legacy Wrapper
How can wrapper services with non-standard contracts be prevented from spreading indirect consumer-to-implementation coupling?
|
|
Policy Centralization
How can policies be consistently processed and enforced across multiple services?
|
|
Proxy Capability
How can a service subject to decomposition continue to support consumers affected by the decomposition?
|
|
Schema Centralization
How can service contracts be designed to avoid redundant data representation?
|
|
Service Decomposition
How can the granularity of a service be increased subsequent to its implementation?
|
|
Service Façade
How can a service be designed to support multiple contracts while maintaining logic-to-contract coupling?
|
|
Service Refactoring
How can a service be evolved without impacting existing consumers?
|
|
Validation Abstraction
How can service contracts be designed to more easily adapt to validation logic changes?
|
|
|
| Prev | Next
|
|
|
