Categories:
Aura file manager
aura-file-manager is the microservice in charge of uploading a file to a temporary repository, validating it and returning a link as validation result.
Find in the current documents the description of this component, its architecture, components and processes.
Aura Virtual Assistant component
Introduction
aura-file-manager is a microservice based on a REST API with the capability of uploading a file to a temporary repository, validating it, and returning a direct download link as validation result.
aura-file-manager uses an utility, aura-file-validator for the validation of files.
Find detailed information regarding Aura file manager in the following documents:
. Architecture and main components
. Communication protocol
. Executed process flowchart and API functionalities
. Environment variables
. API definition
⚠️ In order to use aura-file-manager, it is necessary to activate it previously. Learn how in Aura File Manager activation.
Aura file manager architecture
In the following diagram, the architecture and main components of aura-file-manager are shown:
Internal components
ConfigurationManager
ConfigurationManager is a handler for configuration, obtained through a configuration file or environment variables.
FileService
FileService is where the main functionality of the microservice resides. It is where file upload and validation is done.
HTTP server
Microservice is implemented as an HTTP server (FileManagerServer) that exposes an API to receive the files to be validated.
Middlewares
The route published in the API definition file is handled by a controller but, before a request lands on its controller, it goes through a series of middlewares that provides some common steps needed by all the controllers of the server such as: request validation, common parameters extraction, logging, metrics initialization, etc.
Queue messages processing
Queuing system that allows tolerance to server failures, storing the received files in a DB and processing them later.
Communication protocol
aura-file-manager communication protocol is completely asynchronous, this means that the answer of a request is not included in the HTTP response related to the request, but it is sent as a new HTTP request to the callback aura-bridge.
