Versions Compared

Old Version 2

changes.mady.by.user Nico

Saved on

compared with

New Version 3

changes.mady.by.user Nico

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Provide authentication keys for microservices (as opposed to user-based authentication keys)
    1. 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.
  2. Categorize microservices together
    1. Provides ways to register and query as such a category
      1. This allows things such as front-ends to know which services are available and only show those in the user interface.
      2. 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
      3. 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
  3. Query for frontend modules/pages
    1. 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"
    2. Currently it uses a hack to register these pages to the core


Use (to be filled)

Code

API

Questions

I (Derk Snijders) read Micro service - communication, went through the code and looked at the API, yet still had some questions. Answering these should provide solid documentation as to how to use the registry.

...