12.1.2.1 Dev Backend Service

A dev backend service is the containerized backend application component within a development stack, configured specifically for local development — bind-mounted source, hot reload, verbose logging — distinct from how that same service would be configured for a production deployment.

A Typical Dev-Configured Backend Service

The backend service's development configuration prioritizes fast iteration over the leaner, more locked-down configuration appropriate for production.

services:
  backend:
    build:
      context: ./backend
      dockerfile: Dockerfile.dev
    volumes:
      - ./backend:/app
    environment:
      - LOG_LEVEL=debug
      - NODE_ENV=development
    command: npm run dev
    ports:
      - "8080:8080"

This configuration prioritizes development convenience — a bind-mounted source directory, verbose logging, a hot-reloading command — over the more minimal, optimized configuration a production deployment would typically use.

Why a Separate Development Dockerfile Often Makes Sense

A development-specific Dockerfile can include additional debugging tools or a different base image variant not needed (and not desirable) in a leaner production image.

FROM node:20
RUN npm install -g nodemon

This development variant includes a hot-reloading tool not needed in production, where the application would instead run its built, optimized output directly.

Connecting the Backend to Its Local Dependencies

The development backend service connects to other locally running dependencies exactly as it would in any other environment, just configured for this specific local context.

environment:
  - DATABASE_URL=postgres://db:5432/app_dev

Why This Dev-Specific Configuration Differs Intentionally From Production

The differences between this development configuration and an eventual production one are deliberate, reflecting the different priorities (fast iteration versus optimized, secure deployment) appropriate to each specific context.

services:
  backend:
    build:
      dockerfile: Dockerfile.prod
    command: node dist/server.js

Why a Dev Backend Service Configuration Matters

Deliberately configuring the backend service for development's specific priorities — fast iteration, convenient debugging — while maintaining a clear, intentional distinction from production configuration, supports both an efficient development workflow and a properly optimized eventual deployment.