Microservice type

To recognize the task of a microservice, we introduced the microservice type. In this way we can dynamically handle microservices by the type.

Config

In metadata of the application.yml of every microservice you can specify the type. In addition to the type, for example, we also enter the friendly name. The following shows a section of the config file of an extractor.

eureka:
  instance:
    metadataMap:
      type: executer
      friendlyname: Executer

Types

In this development stage, for example, any number of "extractor" microservices are allowed. But we only want to have one repo. We predefined the following first set of types.

Type	Count	Task
repo	1	Provides a permanent data store for files
executer	1	Provides methods to execute a workflow
db	1	Provides a permanent data store for rdf tripples
webclient	1	Provides the UI
extractor	any	Provides methods to extract data