What is a stateless worker?

Definition

A stateless worker obtains durable inputs from external storage and may build temporary local state for speed. If the worker disappears, another worker can reconstruct the same state and continue the task.

Repository hosting can use workers that replay a log to materialize Git state on demand. This reduces permanent replica requirements but needs efficient recovery, caching and deterministic assignment.

ELI5

A stateless worker performs a task without treating information stored only on that worker as permanent truth. It retrieves durable inputs from shared storage and can rebuild temporary local state when needed.

For example, a worker can replay a repository log to reconstruct files for a job. If the worker disappears, another one can rebuild the same state and continue, provided recovery and assignment are deterministic.

Does a stateless worker store nothing locally?

It may use caches and temporary files, but correctness does not depend on that local state surviving worker replacement.

Why are stateless workers easier to scale?

They can be added, removed or reassigned without migrating unique durable state from a permanent primary.

  1. Why Git Hosting Is Hard beside a flat diagram of replicated repository servers and a latency bottleneck
Definition card for stateless worker: What is a stateless worker?

A stateless worker performs computation without treating its local state as the durable source of truth, allowing it to be replaced or reassigned.