Information Technology Reference
In-Depth Information
Runtime lifecycle management
We have already reviewed the idea behind the runtime manager and the runtime engine to
understand their purpose. The runtime engine is a grouping of all the running configura-
tions connected together that are provided by the runtime manager. We now need to under-
stand how these components reside in the server and at what times they must be created or
discarded. First of all, let's discuss the runtime manager's lifecycle.
The runtime manager usually behaves like a singleton in an application; we just need one
instance of it. From that one instance, we will construct one or many runtime engines. So, it
is important that even if we create many different runtime managers, they all behave in the
same manner; otherwise, we might have different behaviors depending on how many
runtime managers we have.
In the next section, we will see how different implementations of the runtime manager in-
terface provide solutions for this problem. Whichever implementation we choose, the beha-
vior against the obtained
RuntimeEngine
instance is the same as explained in the fol-
lowing sequence diagram:
