9.1.1.5 Compose Local Orchestration

Compose local orchestration refers to using Compose as a lightweight, single-host orchestration tool — starting, stopping, scaling, and managing a multi-container application's lifecycle — well suited to local development and smaller deployments that don't require the complexity of a full cluster orchestrator like Kubernetes or Swarm.

Managing the Full Application Lifecycle

Compose provides commands covering the entire lifecycle of a multi-container application, from initial startup through ongoing management to eventual teardown.

docker compose up -d
docker compose ps
docker compose logs -f api
docker compose restart api
docker compose down

Why Compose Is Appropriate for Single-Host Scenarios

Compose orchestrates containers on a single host, without the multi-host scheduling, automatic failover, and cluster-wide resource management a full orchestrator like Kubernetes provides — this makes it considerably simpler to set up and use, at the cost of not supporting genuinely distributed, multi-host deployment scenarios.

docker compose up -d --scale worker=3

Even Compose's scaling capability operates within the bounds of the single host it's running on, unlike a cluster orchestrator's ability to schedule replicas across many separate machines.

When Compose Is the Right Choice

For local development, smaller production deployments running comfortably on a single host, or staging environments not requiring multi-host resilience, Compose's simplicity is an advantage rather than a limitation.

docker compose -f docker-compose.prod.yml up -d

When a Full Orchestrator Becomes Necessary Instead

Applications genuinely requiring multi-host deployment, automatic failover across machines, or sophisticated, cluster-wide scheduling outgrow what Compose alone can provide, at which point a tool like Kubernetes becomes the more appropriate choice.

kubectl apply -f deployment.yaml

Why Compose Local Orchestration Matters

Recognizing Compose's specific role as a single-host orchestration tool — simpler and more accessible than a full cluster orchestrator, but correspondingly limited in scope — helps in choosing the right tool for a given deployment's actual scale and resilience requirements.