SOAPatterns.org

Overview
- Introduction
- History
- Acknowledgements
- Podcasts
- Candidate Patterns
- Forms
- Press Releases
- Resources
Compound Patterns
Design Patterns (alphabetical)
Design Patterns (by category)
- Foundational Inventory Patterns
- Logical Inventory Layer Patterns
- Inventory Centralization Patterns
- Inventory Implementation Patterns
- Inventory Governance Patterns
- Foundational Service Patterns
- Service Implementation Patterns
- Service Security Patterns
- Service Contract Design Patterns
- Legacy Encapsulation Patterns
- Service Governance Patterns
- Capability Composition Patterns
  - Capability Composition
  - Capability Recomposition
- Service Messaging Patterns
- Composition Implementation Patterns
- Service Interaction Security Patterns
- Transformation Patterns
- REST-inspired Patterns
Cloud Computing Patterns
Service Technology Specs
SOA School
- Home
- Matrix
- Certifications
- Courses
- Exams
- Self-Study Kits
- Workshops
- Licensing
- Online Store

Home > Design Patterns > Agnostic Context

Agnostic Context (Erl)

How can multipurpose service logic be positioned as an effective enterprise resource?

Problem

Multi-purpose logic grouped together with single purpose logic results in programs with little or no reuse potential that introduce waste and redundancy into an enterprise.

Solution

Isolate logic that is not specific to one purpose into separate services with distinct agnostic contexts.

Application

Agnostic service contexts are defined by carrying out service oriented analysis and service modeling processes.

Impacts

This pattern positions reusable solution logic at an enterprise level, potentially bringing with it increased design complexity and enterprise governance issues.

Principles

Service Reusability

Architecture

Service

Listen to the podcasts that accompany this site

Agnostic Context: The application of this pattern results in a subset of the solution logic being further decomposed and then distributed into services with specific agnostic contexts.

The application of this pattern results in a subset of the solution logic being further decomposed and then distributed into services with specific agnostic contexts.

Related Patterns in This Catalog

Agnostic Capability, Agnostic Sub-Controller, Canonical Expression, Capability Recomposition, Composition Autonomy, Cross-Domain Utility Layer, Entity Abstraction, Logic Centralization, Service Encapsulation, Utility Abstraction

Related Service-Oriented Computing Goals

Increased Business and Technology Alignment, Increased Organizational Agility, Increased ROI, Reduced IT Burden

This page contains excerpts from:

SOA Design Patterns by Thomas Erl

Foreword by Grady Booch

With contributions from David Chappell, Jason Hogg, Anish Karmarkar, Mark Little, David Orchard, Satadru Roy, Thomas Rischbeck, Arnaud Simon, Clemens Utschig, Dennis Wisnosky, and others.

(ISBN: 0136135161, Hardcover, Full-Color, 400+ Illustrations, 865 pages)

For more information about this book, visit www.servicetechbooks.com.