Docker Jobs

Lombok supports Docker-backed execution as a distinct path in the app platform.

This should be understood separately from the primary runtime-worker path.

Two execution modes to distinguish

At a high level, Lombok supports:

• runtime-worker execution through the worker runtime
• Docker-backed execution through Docker-oriented handler and platform services

That distinction matters because Docker is not the default explanation for all app execution.

Source-aligned mental model

The reviewed codebase and Senior Dev review specifically flagged Docker jobs as needing a more concrete explanation.

The important distinction is:

• runtime workers are the normal app-worker execution path
• Docker-backed execution is the path associated with Docker-oriented configuration and handler behavior

The review specifically highlighted concepts such as:

• handler.type: 'docker'
• containerProfiles

Those concepts belong to the Docker-backed path rather than the standard runtime-worker path.

Why this matters

This distinction helps prevent a common documentation mistake:

• overstating Docker as if all app execution is container-first

Instead, Docker jobs should be taught as an optional and distinct execution model inside the larger platform.

Next steps

Continue with:

• App Architecture
• Events & Tasks
• Workers