Select a Pattern Agnostic Capability Agnostic Context Agnostic Sub-Controller Asynchronous Queuing Atomic Service Transaction Brokered Authentication Canonical Expression Canonical Protocol Canonical Resources Canonical Schema Canonical Schema Bus Canonical Versioning Capability Composition Capability Recomposition Compatible Change Compensating Service Transaction Composition Autonomy Concurrent Contracts Contract Centralization Contract Denormalization Cross-Domain Utility Layer Data Confidentiality Data Format Transformation Data Model Transformation Data Origin Authentication Decomposed Capability Decoupled Contract Direct Authentication Distributed Capability Domain Inventory Dual Protocols Enterprise Inventory Enterprise Service Bus Entity Abstraction Event-Driven Messaging Exception Shielding Federated Endpoint Layer File Gateway Functional Decomposition Intermediate Routing Inventory Endpoint Legacy Wrapper Logic Centralization Message Screening Messaging Metadata Metadata Centralization Multi-Channel Endpoint Non-Agnostic Context Official Endpoint Orchestration Partial State Deferral Partial Validation Policy Centralization Process Abstraction Process Centralization Protocol Bridging Proxy Capability Redundant Implementation Reliable Messaging Rules Centralization Schema Centralization Service Agent Service Broker Service Callback Service Data Replication Service Decomposition Service Encapsulation Service Facade Service Grid Service Instance Routing Service Layers Service Messaging Service Normalization Service Perimeter Guard Service Refactoring State Messaging State Repository Stateful Services Termination Notification Three-Layer Inventory Trusted Subsystem UI Mediator Utility Abstraction Validation Abstraction Version Identification Overview     History     Acknowledgements     Podcasts     Notification Form     Feedback Form     Press Release #1     Press Release #2     Press Release #3 Master SOA Design Pattern Catalog     Master Pattern List (alphabetical)     Master Pattern List (by category)     Master Pattern List with Page Numbers (PDF)     Master Pattern List (Text)     Pattern Notation     Pattern Profiles     Symbol Legend     Pattern Contribution Form SOA Candidate Patterns     SOA Patterns Review Committee     Candidate Patterns Overview     Candidate Patterns List     Candidate Pattern Contribution Form     Candidate Pattern Feedback Form     SOA Pattern Template Design Pattern Basics     What's a Design Pattern?     What's a Design Pattern Language?     What's a Compound Pattern? Supplemental     SOA Patterns and Application Technologies     SOA Design Patterns Historical Influences     SOA Design Patterns and Design Principles     SOA Design Patterns and Design Granularity     Legal Resources     Design Patterns Publications     Reference Posters     SOAPrinciples.com     WhatIsSOA.com     SOA Visio Stencil About the Book SOA Design Patterns by Thomas Erl For more information visit: www.soapatterns.com Related Publications "Introducing SOA Design Patterns", SOA World Magazine (PDF) "The Case for Single-Purpose Services: Understanding the Non-Agnostic Context and a Strategy for Implementation", SOA Magazine (HTML) "REST-Inspired SOA Design Patterns", SOA Magazine (HTML) "Service-Orientation and Object-Orientation Part I: A Comparison of Goals and Concepts", SOA Magazine (HTML) "Service-Orientation and Object-Orientation Part II: A Comparison of Design Principles", SOA Magazine (HTML) "Service Facade", InformIT (HTML) "Non-Agnostic Context", InformIT (HTML) "Domain Inventory", InformIT (HTML) "Service Normalization", InformIT (HTML) "Service Decomposition", InformIT (HTML) "Canonical Schema", InformIT (HTML) "Policy Centralization", InformIT (HTML) Entity Data Abstraction (candidate) Home > Candidate Patterns List > Entity Data Abstraction How can a reusable business data architecture be established? Problem Creating data models (schemas) in support of entity services can result in a series of service-specific data models that introduce redundancy and are only useful to the services. Solution Establish an entity data architecture that exists independently from the federated service endpoint layer, so that it can be normalized and used by both services and other parts of the enterprise. Application Entity-centric schemas are defined and standardized separately in support of service layers but also in support of generic data representation. Impacts Not all schemas will be appropriate for all services, which may lead to performance trade-offs or the need to introduce redundant data models. Principles Standardized Service Contract, Service Abstraction Architecture Inventory Status Under Review Contributor Thomas Erl   Contributor Notes Although this technique is common when designing data architectures as independent layers in support of entity service layers, this design pattern seems like more of a mildly specialized implementation of Schema Centralization. I¡¦m not certain whether a separate pattern dedicated to entity schema abstraction is warranted. - Thomas Erl

Home    SOA Books    SOA Magazine    What is SOA?    SOA Principles    SOASchool.com    SOA Glossary	Copyright © 2007-2010 SOA Systems Inc.