Active and Passive
As we established in the State Management in Abstract section earlier, a software program can transition through different states in its lifetime. Our example described two basic states a car was capable of having: in motion and stationary. A software program - or, in this case a service – can also have two comparable, primary states:
The first represents the service being invoked or executed and therefore entering an active state. The latter refers to the period during which the service is not in use and therefore exists in a passive or "non-activate" state.