9.1.2.5 Compose Full Stack Environments

Compose full stack environments describes using a single Compose file to define every layer of an application — frontend, backend API, database, cache, and any other supporting services — providing a complete, runnable representation of the entire stack with one command.

Defining the Complete Stack

Every layer of the application is expressed as its own service within the same Compose file, connected together through Compose's automatic networking.

services:
  frontend:
    build: ./frontend
    ports:
      - "3000:3000"
    depends_on:
      - api
  api:
    build: ./backend
    environment:
      - DATABASE_URL=postgres://db:5432/app
      - CACHE_URL=redis://cache:6379
    depends_on:
      - db
      - cache
  db:
    image: postgres:16
    volumes:
      - pgdata:/var/lib/postgresql/data
  cache:
    image: redis:7

volumes:
  pgdata:

Starting and Verifying the Whole Stack

A single command brings up every layer together, correctly networked and configured.

docker compose up -d
docker compose ps

Reviewing the status of every service together confirms the entire stack started successfully.

Why a Full Stack Definition Is Valuable for Onboarding

A new developer, or anyone evaluating the project for the first time, can have the entire application running locally with a single command, without needing to separately install or configure each individual layer.

git clone https://github.com/example/myapp.git
cd myapp
docker compose up -d

Considering When a Single Compose File Becomes Too Large

As an application grows, a single Compose file describing every layer can become unwieldy — splitting into multiple Compose files (combined using Compose's file-merging capability) can help manage this growing complexity while still preserving the benefit of a complete, runnable definition.

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

Why Compose Full Stack Environments Matter

Defining an application's complete stack within Compose provides an accurate, runnable, and easily shared representation of the entire system, significantly lowering the barrier to getting a full local environment running and understood.