How to Use Docker for Local Microservices Development: A Practical Guide

Developing microservices locally can be a hassle when you need to run multiple services with different dependencies. Docker simplifies this by letting you containerize each service and orchestrate them with Docker Compose. This tutorial walks you through setting up a local development environment that mirrors production.

First, create a docker-compose.yml file in your project root. Define each microservice as a separate service under the services key. For example, a Node.js API and a Python worker:

Article illustration

version: '3.8'
services:
  api:
    build: ./api
    ports:
      - "3000:3000"
    volumes:
      - ./api:/app
  worker:
    build: ./worker
    volumes:
      - ./worker:/app

1. Speed Up Development with Bind Mounts

Use volumes to mount your source code into the container. This enables live reload—any change you make on your host is instantly reflected inside the container. For Node.js, run npm run dev with a watcher like nodemon. For Python, use uvicorn --reload.

2. Manage Environment Variables Securely

Store per-service variables in separate .env files. In your compose file, reference them with the env_file directive:

services:
  api:
    env_file: ./api/.env

Never commit .env files containing secrets. Use .env.example in your repo instead.

3. Handle Inter‑Service Communication

Docker Compose creates a default network so services can reach each other by service name (e.g., http://api:3000). No need to hardcode IPs. For databases, add a depends_on clause to control startup order.

4. Debug with Logs and Interactive Shells

Run docker-compose logs -f to tail logs from all services. For debugging a specific service, open an interactive shell: docker-compose exec api sh. You can install tools like curl or netcat inside the container for network testing.

Conclusion: Docker Compose with bind mounts, proper environment handling, and built-in networking turns local microservices development into a smooth, reproducible process. Start small, add services as needed, and you’ll avoid the “it works on my machine” problem.

sarah antaboga
Author: sarah antaboga

Leave a Reply

Your email address will not be published. Required fields are marked *