Document service state management requirements as you become aware of them. This can be documented either in
the service model itself, or in a separate requirements document.
See Guideline: State Management for Services for advice on common scenarios
that result in the need for stateful services.
Further, composite service participants often have requirements to maintain state information across the
invocation of the composed services. The service choreographer often is responsible for managing the state.
Finally, a component that implements and realizes multiple related services or operations on services might need to
maintain state between invocations for performance reasons.
|