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 > Validation Abstraction

Validation Abstraction (Erls)

How can service contracts be designed to more easily adapt to validation logic changes?

Problem

Service contracts that contain detailed validation constraints become more easily invalidated when the rules behind those constraints change.

Solution

Granular validation logic and rules can be abstracted away from the service contract, thereby decreasing constraint granularity and increasing the contract's potential longevity.

Application

Abstracted validation logic and rules need to be moved to the underlying service logic, a different service, a service agent, or elsewhere.

Impacts

This pattern can somewhat decentralize validation logic and can also complicate schema standardization.

Principles

Standardized Service Contract, Service Loose Coupling, Service Abstraction

Architecture

Service

Validation Abstraction: By reducing the overall quantity of constraints and especially filtering out those more prone to change, the longevity of a service contract can be extended.

By reducing the overall quantity of constraints and especially filtering out those more prone to change, the longevity of a service contract can be extended.

Related Patterns in This Catalog

Compatible Change, Concurrent Contracts, Entity Abstraction, Partial Validation, Policy Centralization, Rules Centralization, Schema Centralization, Service Agent, Service Refactoring

Related Service-Oriented Computing Goals

Increased Federation, 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.

This page contains excerpts from:

Web Service Contract Design and Versioning for SOA

by Thomas Erl, Anish Karmarkar, Priscilla Walmsley, Hugo Haas, Umit Yalcinalp, Canyang Kevin Liu, David Orchard, Andre Tost, James Pasley

Foreword by David Chappell

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.

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