Return to Home Page
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)





Canonical Data Format (candidate)


Home > Candidate Patterns List > Canonical Data Format

How can services be designed to avoid data format transformation?

Problem

Services that use different formats to represent data cause interoperability concerns, raise difficult runtime exceptions, and require the need for undesirable data format transformation measures.

Solution

The format used to deliver data between services is standardized across all services within an inventory, thereby guaranteeing a base level of interoperability.

Application

Depending on the communication protocols being used, this pattern may dictate certain file formats or, in the case of Web services, the use of the WS-I Basic Profile.

Impacts

Data format standardization can lead to communication limitations associated with the chosen format type.

Principles

Standardized Service Contract

Architecture

Inventory

Status

Under Review

Contributor

Thomas Erl
 

Contributor Notes

While there¡¦s not harm in standardizing on common data formats, this form of standardization may not warrant a separate design pattern. Data Format Transformation is often carried out within service boundaries to overcome legacy compliance issues. In many of these situations, the data formats cannot be standardized until the legacy system is replaced. Also, the application of Canonical Protocol often will result in the standardization of data formats that are established with the communication protocol technology.

- Thomas Erl

The Prentice Hall Service-Oriented Computing Series from Thomas Erl
Home    SOA Books    SOA Magazine    What is SOA?    SOA Principles    SOASchool.com    SOA Glossary Copyright © 2007-2010
SOA Systems Inc.