SOA Glossary - passive (primary state)

NEWS >>

<< NEWS

This glossary supports the following titles:

SOA Design Patterns

Web Service Contract Design & Versioning for SOA

SOA Principles of Service Design

Service-Oriented Architecture: Concepts, Technology, and Design

Modern SOA Infrastructure: Technology, Design, and Governance

SOA with REST

Next Generation SOA: A Real-World Guide to Modern Service-Oriented Computing

SOA with .NET & Azure

SOA with Java

SOA Governance

SOA Security: Practices, Patterns, and Technologies for Securing Services

SOA and Cloud Computing: Practices, Patterns, Technologies

This glossary also supports the SOA Certified Professional (SOACP) program.

For more information, visit: www.soacp.com
and
www.soaschool.com

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.