Home > SOA Glossary > Passive (Primary State)

Passive (Primary State)

A service that has been loaded into memory but is not actively carrying out any of its functions is considered to exist in a passive state. Services may run idle (be passive) prior to and subsequent to invocation and execution.

Note that passive services are always stateless. In fact, services may be designed to intentionally enter a passive state after having deferred state data to another part of the architecture. Such services may return to an active state at a later point to continue processing associated with the same service activity.

The term "passive" represents one of two primary states a service can exist as, the other being active. Primary states are of relevance to the implementation of the Service Statelessness principle that emphasizes the optimization of state data deferral and delegation.


See also: