-
Type:
Sub-task
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: ADDONS_9.10
Engine is a singleton object. Such pattern has been chosen for better control over container execution and memory control through app lifecycle.
Engine consists of 3 parts.
1. Mapper.
a. Receives JSON from web layer
b. Maps received parameters to expected by execution container.
c. Returns these parameters
2. Runner
a. Has access to a dispatching queue that based on configuration of the application keeps running containers under defined maximum.
b. Schedules execution of the containers from received Task objects
3. Caller
a. Accepts messages of successful completion from the containers with output parameters. Sends POST request to an external URL with results of execution.