ID Number: G00170094



Data Consistency and SOA: Old Challenges Rear Their Ugly Heads
18 September 2009
 
Daniel Sholler   W Schulte  

As organizations apply service-oriented architecture to their designs, they are faced with many challenges that previously had been the province of massively distributed systems. These challenges, such as how to manage data consistency, demand rethinking some long-held assumptions.




Price: US$495.00

Pages: 10






Browse Topics


Other Options







Contact Gartner





Purchasing this document is fast, easy and secure, but you must be registered with gartner.com so we can track your order. Please select your status from these three choices:
Registration is required to purchase this document.
Or, you can register for gartner.com only.
 You or your organization may already own this document. Register now to find out. Your Gartner Membership Administrator can supply the needed License Key(s).
You will not lose your document during registration.
Sign in here:
Username:

Password:
Forgot your username
or password?







For more information about purchasing this or other documents, contact Gartner at one of the telephone numbers below:
North America:    +1 203-316-3010 7:30 am - 8:00 pm Stamford, CT
Europe:    +44 1784 267770 9:00 am - 5:00 pm London
Asia/Pacific:    +65 6879 2785 9:00 am - 6:00 pm Singapore
Japan:    +81 3 3481 3552 9:00 am - 5:30 pm Tokyo

Table of Contents


    
 Analysis

1.0
    
 Introduction: Sharing Data
2.0
    
 Why Shared Data Becomes More Difficult With SOA

2.1
    
 Data Consistency and Business Outcomes
2.2
    
 What We Know About Consistent Data and Consistent Outcomes
3.0
    
 Why Data Consistency Is a Problem for Distributed Systems

3.1
    
 CAP Theorem
3.2
    
 Definitions of Consistency Aren't Consistent
3.3
    
 Boundaries
3.4
    
 Client Versus Server
4.0
    
 Data Consistency Models

4.1
    
 ACID
4.2
    
 Eventual Consistency
5.0
    
 Likelihood of Error and Cost of Repair

5.1
    
 Questions of ACID Versus Eventual Consistency
6.0
    
 General Recommendations for Data Consistency Uses

6.1
    
 Use ACID Transactions When There's a Reference Copy of the Data
6.2
    
 Use Mediated Eventual Consistency to Manage Distributed, Low-Volatility Data, Such as Master Data
6.3
    
 Build Explicit Consistency Into the Processes When Managing Complex, Long-Running Interactions
6.4
    
 Build Services to Tolerate Repetition
7.0
    
 Recommendations

7.1
    
 Build Explicit Consistency Assumptions Into Application Requirements
7.2
    
 Identify Information Boundaries, Particularly Where Replication Occurs
7.3
    
 Use Information Flow Models to Map Consistency Requirements
7.4
    
 Build Defensive Compensation Techniques Into Services

    
 Recommended Reading




Browse Topics:
 
Service-Oriented Architecture
Data Management and Integration




© 2009 Gartner, Inc. and/or its Affiliates. All Rights Reserved. Reproduction and distribution of this publication in any form without prior written permission is forbidden. The information contained herein has been obtained from sources believed to be reliable. Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information. Although Gartner's research may discuss legal issues related to the information technology business, Gartner does not provide legal advice or services and its research should not be construed or used as such. Gartner shall have no liability for errors, omissions or inadequacies in the information contained herein or for interpretations thereof. The opinions expressed herein are subject to change without notice.




Resource Id: 1183313