Multi-Container Apps with Compose
EK, REAL-WORLD, application, mein, USUALLY, MULTIPLE, SERVICES, hoti, HAIN: EK, FRONTEND, (React/Vue), EK, BACKEND, API, (Node/Python), EK, DATABASE, (Postgres/MySQL), aur, KABHI-KABHI, EK, CACHE, LAYER, (Redis). Compose, se, YE, SAARI, services, EK, SAATH, DEFINE, ki, ja, sakti, HAIN.
HAR, service, apne, ISOLATED, container, mein, chalti, hai, LEKIN, SAB, EK, SHARED, Compose, NETWORK, PAR, hoti, HAIN, ISLIYE, SERVICE, NAAM, se, hi, EK, DOOSRE, se, TALK, kar, sakti, HAIN (jaise, "redis" ya, "postgres").
services:
frontend:
build: ./frontend
ports:
- "80:80"
backend:
build: ./backend
ports:
- "3000:3000"
environment:
- DATABASE_URL=postgres://user:pass@postgres:5432/app
- REDIS_URL=redis://cache:6379
depends_on:
- postgres
- cache
postgres:
image: postgres:16
volumes:
- db-data:/var/lib/postgresql/data
cache:
image: redis:7-alpine
volumes:
db-data:- Real apps mein frontend, backend, database, cache alag containers hote hain
- Sab ek shared Compose network par service naam se connect hote hain
- Ek command se poora multi-service stack khada ho jaata hai
"docker compose up --scale service_name=3" se, EK, service, ke, MULTIPLE, INSTANCES, (replicas) LOCAL, mein, bhi, RUN, kiye, ja, sakte, HAIN — LEKIN, LOAD, BALANCING, ke, liye, EXTRA, SETUP, (jaise, nginx, reverse, proxy) ZAROORI, hota hai.
docker compose up --scale backend=3 -dSAARI, services, JO, EK, hi, docker-compose.yml, mein, DEFINE, hoti, HAIN, WO, AUTOMATICALLY, EK, SHARED, network, PAR, hoti, HAIN — HAR, service, apne, "service, NAAM" se, hi, DOOSRI, services, ko, RESOLVE, kar, sakti, hai.