4baf9527d7
This turned out to be very difficult to do in small isolated steps. * Design overhaul of the control gui using bootstrap * Move the actors out of control-service into to a new executor-service, that can be run on multiple nodes * Add node-affinity to message queue |
||
|---|---|---|
| .. | ||
| src | ||
| build.gradle | ||
| readme.md | ||
Control Service
The control service provides an operator's user interface, and is responsible for orchestrating the various processes of the system using Actors.
Actors within the control service will spawn processes when necessary, by monitoring their message queue inboxes.
Central Classes
- ControlService
- ControlActors - Class responsible for Actors' lifecycle
- ProcessService - Class responsible for spawning Processes
See Also
- processes
- libraries/message-queue - The Message Queue and Actor abstractions