Flow control

Application initialisation begins inside the Manager class which, after some work, passes control to a plugin. When this finishes, initialisation is virtually complete.

Which plugin does it pass control to? Whichever plugin implements IManagerLifeCycle. If the application is cold-starting then its coldStart() method is called. If the application is warm-starting its warmStart() method is called.

We can see from Figure  that no IManagerLifeCycle plugin is supplied with the Manager netlet. This means we have to implement it ourselves and make sure we add it into the Manager netlet.

After the IManagerLifeCycle has completed this, work flow control is event-driven. The other plugins, and indeed the IManagerLifeCycle plugin, are called in response to third parties binding services, worker checks, etc. These plugins are most likely to call other plugins to help in their work.