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 > Service Data Replication

Service Data Replication (Erl)

How can service autonomy be preserved when services require access to shared data sources?

Problem

Service logic can be deployed in isolation to increase service autonomy, but services continue to lose autonomy when requiring access to shared data sources.

Solution

Services can have their own dedicated databases with replication to shared data sources.

Application

An additional database needs to be provided for the service and one or more replication channels need to be enabled between it and the shared data sources.

Impacts

This pattern results in additional infrastructure cost and demands, and an excess of replication channels can be difficult to manage.

Principles

Service Autonomy

Architecture

Inventory, Service

Service Data Replication: By providing each service its own replicated database, autonomy is increased and the strain on the shared central database is also reduced.

By providing each service its own replicated database, autonomy is increased and the strain on the shared central database is also reduced.

Related Patterns in This Catalog

Composition Autonomy, Distributed Capability, Legacy Wrapper, Proxy Capability, Redundant Implementation

Related Service-Oriented Computing Goals

Increased Vendor Diversification Options, 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.