|
|
Master SOA Design Pattern Catalog
|
|
|
|

Stateful Services (Erl)

|

Home > Inventory Implementataion Patterns > Stateful Services
|
|
How can service state data be persisted and managed without
consuming service runtime resources?
|
|
|
|
|

Problem

State data associated with a particular service activity can impose
a great deal of runtime state management responsibility upon
service compositions, thereby reducing their scalability.
|
|

Solution

State data is managed and stored by intentionally stateful utility
services.
|
|

Application

Stateful utility services provide in-memory state data storage
and/or can maintain service activity context data.
|
 |
 |
 |

Impacts

If not properly implemented, stateful utility services can become
a performance bottleneck.
|
|
|
|
|
|


|
With the use of stateful utility services, state management responsibilities are deferred.

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