...
- Provide authentication keys for microservices (as opposed to user-based authentication keys)
- This allows microservices to communicate between each other without the approval of a user (action). This is useful (needed) for things such as cron tasks.
- Categorize microservices together
- Provides ways to register and query as such a category
- This allows things such as front-ends to know which services are available and only show those in the user interface. TODO discuss this
- In the case of the application microservice, this allows for several microservice of the category "application" to be grouped together and used interchangeably for the same thing within oms-events
- In the case of the notification pipeline, we will also have several microservices of the category "notification" which either send notifications via mail or push or smoke signals or whatever
- Provides ways to register and query as such a category
- Query for frontend modules/pages
- Each microservice can register modules/pages/whatever-we-call-them to be displayed additionally in the menu bar and also be loaded upon frontend load. The registry gathers these by a registered getModules.json (the path to this file is set with a label, see "Use"
- Currently it uses a hack to register these pages to the core
- In the future it might take over the modules functionality from the core, doing effectively the same thing TODO discuss this
...