Overview of the Arroyo architecture
arroyo
which provides sub-commands to run specific services or an entire Arroyo cluster.
This document will cover the subsystems that make up an Arroyo cluster.
controller.scheduler
config key.
arroyo node
processes (for example, in an autoscaling group) and configure them with the controller’s
address. The controller will then schedule workers on these nodes.
Created
state when they are created via the API. Once the controller loads the job, it
will begin managing it, and is responsible for moving it to a terminal state (like Running, Stopped, Failed) within a
bounded amount of time.