Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions architecture.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ The Arroyo system architecture is composed of several services, as can be seen i

![Arroyo Architecture](/images/arroyo_arch.png)

These services can be run in a single process for a simple deployment, or separately for a fully scaleable,
These services can be run in a single process for a simple deployment, or separately for a fully scalable,
fault-tolerant system. All components of the system are compiled into a single binary `arroyo`
which provides sub-commands to run specific services or an entire Arroyo cluster.

Expand Down Expand Up @@ -36,7 +36,7 @@ There is a single controller instance that runs in the system, and high-availabi
source release. If the controller instance fails, the workers will eventually stop and wait for the controller to come
back online.

The controller manages a state machine for each job, which is documented [here](#state-machine) and is also responsible
The controller manages a state machine for each job, which is documented [here](#job-state-machine) and is also responsible
for initiating checkpoints on the workers. Communication between the controller and workers is done via the gRPC API
defined in [rpc.proto](https://github.com/ArroyoSystems/arroyo/blob/master/arroyo-rpc/proto/rpc.proto).

Expand Down