|
|
Master SOA Design Pattern Catalog
|
|
|
|

State Repository (Erl)

|

Home > Inventory Implementataion Patterns > State Repository
|
|
How can service state data be persisted for extended periods
without consuming service runtime resources?
|
|
|
|
|

Problem

Large amounts of state data cached to support the activity within
a running service composition can consume too much memory,
especially for long-running activities, thereby decreasing
scalability.
|
|

Solution

State data can be temporarily written to and then later retrieved
from a dedicated state repository.
|
|

Application

A shared or dedicated repository is made available as part of the
inventory or service architecture.
|
 |
 |
 |

Impacts

The addition of required write and read functionality increases
the service design complexity and can negatively affect
performance.
|
|
|
|
|
|


|
By deferring state data to a state repository, the service is able to transition to a stateless
condition during pauses in the activity, thereby temporarily freeing system
resources.

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