|
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 5: Basic Service Inventory Design Pattern Language

|
Home >
Chapter 5 Overview >
5.1 Inventory Context Design Patterns

|
Inventory Context Design Patterns

Establishing the overarching architectural context of a particular environment is foundational to the ultimate implementation of the technology architecture.


The core Business-Driven Context and Vendor-Agnostic Context patterns (Figure 5.x) establish baseline characteristics that set a strategic direction for an inventory architecture by positioning it in such a manner that it can continually evolve with the business while leveraging on-going technology innovation.

These patterns are ideally applied early on in the definition stages as they help determine both the nature and direction of an inventory architecture. At the same time, their application can also impose limitations that may need to be planned for as well.

This section covers the following design patterns:
Business-Driven Context

How can a technology architecture be designed to remain in alignment with changing business goals and
requirements?
|
|

Vendor-Agnostic Context

How can a technology architecture be designed to avoid inhibiting dependencies on proprietary vendor platforms?
|
|

|
|
Prev | Next
|
|
|