Overview

The Worker Manager (or rs-worker-manager) microservice has been designed to manage light treatments, scalable, hot-deployable and specific for missions. Treatments are realized by standalone applications named worker.

rs-worker-manager responsibilities:

• manage the cycle of life of workers
• send requests to workers, retry request in error
• monitor treatments realized by workers
• manage a workflow of workers, the output of one worker is the input for the next

Concept	Compatibility	Description
Multitenant	Yes	Can handle multiple tenants/projects
Vertical scalability	Yes	Uses Jobs system
Horizontal scalability	Yes	Service can not be deployed with multiple instances

You can learn how the service works with the How it works section.

How to use

You can learn how to operate with the microservice thanks to API Guides :

• Publish a request to rs-worker-manager using AMQP API
• Listen responses from rs-worker-manager after publishing a request to rs-worker-manager using AMQP API
• Browse all REST API available endpoints for administration and monitoring treatments realized by rs-worker-manager, workers

You can learn how to operate with a worker thanks to API Guides :

• Indicate to rs-worker-manager, the worker is alive using AMQP API
• Subscribe to requests from worker-manager using AMQP API
• Publish a response to rs-worker-manager using AMQP API

How to configure

The rs-worker-manager microservice manage workers with a configuration file. This file is used to configure the types of worker and worker workflow accepted.

To learn how the microservice is configured with static parameters from properties files see Configuration section.

To understand the configuration of specific tenant (aka project). see Import/export configuration section.

How to access source code

Microservice source code is available on GitHub.