The carbon registry seems to have multiple purposes in the WSO2 carbon platform. It would be useful to understand the high level use cases that the registry is used for. Here are some that I can think of:
- Storing internal WSO2 product configuration for clustering, etc
- Storing configuration data for shaing between custom applications or services
- As a content repository for WSO2 governance server, e.g. for wsdls, documents, etc
Are these use cases correct? Are there any more use cases?
Is it appropriate to think of the carbon registry as providing similar functionality to windows registry but it is also accessible remotely?