|
|
Master SOA Design Pattern Catalog
|
|
|
|

Service Data Replcation (Erl)

|

Home > Service Implementation Patterns > Service Data Replication
|
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.
|
|
|
|
|
|


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

|
|
|
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.soabooks.com.
|
|