Kif taħdem in-networks Docker b'ħarsa profonda?

Question

IT Interview Practice · Accepted Answer

Docker jipprovdi diversi **network drivers** (bridge, host, overlay, macvlan, none) għal ħtiġijiet ta' konnettività differenti, flimkien ma' features bħal **user-defined networks** bid-DNS-based service discovery. Jifhem in-networking b'ħarsa profonda huwa importanti għall-konnessjoni ta' applikazzjonijiet multi-container u multi-host korrettament.

## Network drivers

```text
BRIDGE (default) → a private internal network on a single host; containers communicate;
  isolated from the host except via published ports. USER-DEFINED bridges add DNS
  (containers reach each other by name) — preferred over the default bridge.
HOST → the container uses the host's network stack directly (no isolation, no port
  mapping needed) — max performance, less isolation.
OVERLAY → spans MULTIPLE hosts → containers on different machines communicate
  (for Docker Swarm / multi-host clusters).
MACVLAN → gives a container its own MAC/IP on the physical network (appears as a
  physical device).
NONE → no networking (fully isolated).
```

## User-defined networks u service discovery

```bash
docker network create app-net
docker run -d --name db --network app-net postgres
docker run -d --name api --network app-net myapi
# → on a user-defined network, Docker's embedded DNS resolves container NAMES
#   the "api" reaches the database at hostname "db" → automatic service discovery
```

User-defined networks jipprovdu **automatic DNS-based service discovery** (containers jistgħu jilħqu lil xulxin bl-isem) u iżolazzjoni aħjar mir-default bridge — l-approċċ iracommandati għal apps multi-container.

## Network isolation u segmentation

```text
→ Containers can be placed on DIFFERENT networks to isolate them (segmentation):
  e.g. a frontend network and a backend network; only certain containers bridge both
→ Improves security (a container only reaches what it's networked with)
→ Published ports (-p) are the controlled boundary to the outside world
```

## Għaliex dan huwa importanti

Jifhem in-networking Docker b'ħarsa profonda huwa importanti għall-**konnessjoni ta' applikazzjonijiet multi-container u multi-host korrettament u secure**, għalhekk huwa għarifa praktika valida barra mill-basics.
"}}

Network drivers

User-defined networks u service discovery

Network isolation u segmentation

Għaliex dan huwa importanti

Mistoqsijiet relatati