SOA Patterns > Inventory Centralization Patterns > Schema Centralization
Schema Centralization (Erl)
How can service contracts be designed to avoid redundant data representation?
Problem
Different service contracts often need to express capabilities that process similar business documents or data sets, resulting in redundant schema content that is difficult to govern.
Solution
Select schemas that exist as physically separate parts of the service contract are shared across multiple contracts.
Application
Up-front analysis effort is required to establish a schema layer independent of and in support of the service layer.
Impacts
Governance of shared schemas becomes increasingly important as multiple services can form dependencies on the same schema definitions.
Principles
Architecture
Inventory, Service
WSDL definitions that share common XML schemas end up sharing the same message data models. Note how the reduction of redundant content also results in smaller-sized schemas.
Related Patterns in This Catalog
Canonical Schema, Contract Centralization, Service Normalization, Validation Abstraction
Related Service-Oriented Computing Goals
Increased Business and Technology Alignment, Increased Intrinsic Interoperability, Reduced IT Burden
This pattern is covered in SOACP Module 7: Advanced SOA Design & Architecture with Services & Microservices.
For more information regarding the SOA Certified Pofessional (SOACP) curriculum,
visit www.arcitura.com/soa.
This page contains excerpts from:
SOA Design Patterns by Thomas Erl
(ISBN: 0136135161, Hardcover, Full-Color, 400+ Illustrations, 865 pages)
For more information about this book, visit www.arcitura.com/books.
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
For more information about this book, visit www.arcitura.com/books.