docker-compose for services in Spring Boot - Performance & Optimization

Performance: docker-compose for services

MEDIUM IMPACT

This affects the startup time and resource usage of multiple backend services running together, impacting initial load and responsiveness.

Running multiple Spring Boot services together for development

Spring Boot

version: '3.8'
services:
  service1:
    build: ./service1
    ports:
      - "8080:8080"
  service2:
    build: ./service2
    ports:
      - "8081:8081"
    depends_on:
      service1:
        condition: service_healthy
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8080/actuator/health"]
      interval: 10s
      retries: 5

Using Docker healthchecks allows Docker to manage service readiness without blocking container startup commands.

📈 Performance GainEnables parallel container startup and reduces blocking delays, improving overall startup speed.

Running multiple Spring Boot services together for development

Spring Boot

version: '3.8'
services:
  service1:
    build: ./service1
    ports:
      - "8080:8080"
  service2:
    build: ./service2
    ports:
      - "8081:8081"
    depends_on:
      - service1
    command: ./wait-for-it.sh service1:8080 -- java -jar app.jar

Sequential startup with wait scripts delays overall readiness and blocks parallel container initialization.

📉 Performance CostBlocks startup for service2 until service1 is ready, increasing total startup time by several seconds.

Performance Comparison

Pattern	Container Startup	Blocking	Resource Usage	Verdict
Sequential wait-for-it script	Serial startup	Blocks dependent services	Higher due to idle wait	[X] Bad
Healthcheck with depends_on	Parallel startup	Non-blocking	Efficient resource use	[OK] Good

Rendering Pipeline

Docker-compose orchestrates container startup and networking before the Spring Boot services begin handling requests, affecting backend readiness but not browser rendering directly.

→Container Initialization

→Service Startup

→Network Setup

⚠️ BottleneckService startup blocking due to improper dependency handling

Optimization Tips

1Avoid blocking dependent services with scripts; use Docker healthchecks instead.

2Configure healthchecks to allow parallel container startup and faster overall readiness.

3Monitor container health and startup logs to detect and fix startup delays.

Performance Quiz - 3 Questions

What is a performance downside of using a wait-for-it script in docker-compose for dependent services?

A It reduces container image size

B It blocks dependent services from starting until the main service is ready

C It improves network latency between services

D It automatically scales services

DevTools: Docker CLI and docker-compose logs

How to check: Run 'docker-compose up' with logs enabled; observe service startup order and delays; use 'docker ps' to check container states and health status.

What to look for: Look for containers stuck in starting or unhealthy states indicating blocking or failed healthchecks.