Hmmm, did you consider other alternatives to this solution, which kinda pollutes the `ClusterRegistry` implementation?

IOW, if no active component (based on what the configuration and intercepton chain factory sets up...) depends on `ClusterRegistry`, this component won't be started up. If, one component depends on `ClusterRegistry` and it's started, so it must use it somehow... so, why not the cache be started in `ClusterRegistry`'s `@Start` method implementation?

The component model we have is already lazy in the sense that it only starts those components that a cache will need. We should not try to replicate this logic in a different way.