Skip to main content
Version: 2.1.0

REGARDS downloader microservice

The Downloader or rs-downloader microservice is an integral part of the functional group Restitution services.

rs-downloader is the service that manages downloads of products files.

The downloader microservice can handle online and nearline storage locations. To do so, it uses the same plugins as the storage microservices.

Its main responsibilities are:

  • Downloading files
  • Manage user download quotas

Unlike other microservices, the Downloader microservice is not intended to be accessed directly by users. The REST APIs are mainly private. Instead, file download requests are handled by the Order microservice or the Catalog microservice. The stored files cannot be accessed through the API because the files access rights are not managed by the downloader microservice but by the Data Manager and Catalog microservices.

The Downloader microservice depends on storage plugins, which serve as interfaces between the microservice and the downloader system in use (local, online, or nearline).

ConceptCompatibilityDescription
MultitenantYesCan handle multiple tenants/projects
Vertical scalabilityNoService does not use Jobs system
Horizontal scalabilityYesService can be deployed with multiple instances

You can learn how the service works with the conception section.

How to use

You can learn how to operate the microservice using the API Guides :

Plugins

A storage location plugin serves as the interface between the microservice and the actual storage space (COTS). See the Storage plugins section to learn more about the available storage location plugins and how to configure them.

How to configure

There is no configuration dedicated to the downloder microservice. Storages locations are configured through storage microservice

How to access source code

Microservice source code is available on GitHub. The source code is the same as the storage service. The only difference is the bootstrap module with a specific downloader active profile to enable or disable REST and AMQP controllers.