Overview
Overview
The main objective of the Processing
microservice is to apply treatments to ordered data files,
before they are served to the end user. This service is driven by Order
microservice as describe in Functional overview - Product Restitution services
This service runs as follows:
- Receives processing requests from the
Order
service through AMQP. - An executable is launched, and its execution generates steps.
- The steps are notified
- An execution result is sent to the
Order
microservice. - After the files have been processed, they are available to be downloaded by the user.
Concept | Compatibility | Description |
---|---|---|
Multitenant | Yes | Can handle multiple tenants/projects |
Vertical scalability | Yes | Uses Jobs system |
Horizontal scalability | No | 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 :
- Process : API to list/find existing processes
- Batch : API to create batches
- Monitoring : API to monitor existing executions
- Rights Plugin Configurations : API to manage processes as plugins
Plugins
The list of the different suitable plugins and their configuration are available at the following documentation: Processing plugins
How to configure
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 through UI
You can follow the User manuel to learn about the administrator HMI related functionalities :
How to access source code
Microservice source code is available on [GitHub](https://github. com/RegardsOss/regards-backend/tree/master/rs-processing).