Runtime adapters
Choose the right runtime adapter for your deployment: InProcess, LocalProcess, Docker, HTTP, Remote, or ShardRouter.
Runtime adapters
Runtime adapters determine how app instances are spawned and managed.
Available adapters
| Adapter | Use case |
|---|---|
InProcessRuntime | Development — runs the app in the same process |
LocalProcessRuntime | Production single machine — spawns a child process via stdio |
DockerRuntime | Isolation — runs the app in a Docker container |
HttpDockerRuntime | Isolation with HTTP transport |
RemoteRuntime | Distributed — connects to a remote Execution Host |
ShardRouterRuntime | Horizontal scaling — routes requests across multiple hosts |
Choosing an adapter
- Local dev:
InProcessRuntime— fastest, hot reload - Single machine prod:
LocalProcessRuntime— process isolation, simple - Multi-tenant prod:
DockerRuntime— full container isolation - Distributed prod:
RemoteRuntime+ShardRouterRuntime— scale across machines
Next steps
- Execution Host — distributed deployment
- Controller configuration — set the runtime in config