Container-to-Container Communication
Jab, MULTIPLE, containers, EK, hi, CUSTOM, bridge, network, PAR, hote, HAIN, TO, WO, EK, DOOSRE, se, DIRECTLY, container, NAAM, use, karke, COMMUNICATE, kar, sakte, HAIN — bina, port, mapping, ya, EXTERNAL, ACCESS, ki, ZAROORAT, ke.
YE, MULTI-CONTAINER, applications, (jaise, EK, web, app, jo, DATABASE, se, TALK, karti, hai) mein, BAHUT, COMMON, PATTERN, hai — WEB, app, container, "postgres" naam, ke, hostname, PAR, DATABASE, se, CONNECT, kar, sakta, hai, agar, DONO, SAME, network, PAR, hain.
docker network create app-network
docker run -d --network app-network --name postgres-db \
-e POSTGRES_PASSWORD=secret postgres
docker run -d --network app-network --name web-app \
-e DATABASE_URL=postgres://postgres:secret@postgres-db:5432/mydb \
my-web-app- Same custom network par containers naam se ek doosre ko resolve karte hain
- Multi-container apps (web + db) mein ye standard communication pattern hai
- Container-to-container talk ke liye port mapping ki zaroorat nahi hoti
Docker, Compose, AUTOMATICALLY, EK, DEFAULT, network, banata hai, HAR, project, ke, liye, aur, SAARI, services, ko, USME, JOD, deta hai — MANUALLY, "docker network create" karne, ki, ZAROORAT, NAHI, PADTI.
"networks" section, mein, "aliases" se, EK, container, ko, MULTIPLE, NAMES, se, ACCESSIBLE, banaya, ja, sakta hai — USEFUL, hai, JAB, LEGACY, code, EK, ALAG, HOSTNAME, EXPECT, karta hai.
services:
db:
image: postgres
networks:
default:
aliases:
- database
- postgres-server