Currently we have a number of "service" caches which store additional information about "primary" caches (e.g. protobuf schemas, indexes, topology). We might also want to store other additional information (configurations, metadata, etc).
I think we can hijack the ClusterRegistry class to provide a standardized interface to obtain "service" caches based on a set of requirements (persistent/volatile, shared/private, etc) and apply well-defined configurations to them (e.g. security).