transport layer
The layer that carries data between programs on two machines, identified by port numbers, using TCP or UDP.
In more detail
TCP adds connections, ordering and retransmission; UDP sends independent datagrams. A load balancer working at this layer sees only addresses and ports, not the application's requests. Refused, timed-out and reset connections are transport-layer observations.
Related terms
- TCP — The internet protocol that delivers data between programs reliably and in order, used by the web and most databases.
- UDP — A simple internet protocol that sends messages without guaranteeing delivery or order, used by DNS and streaming.
- port — A number from 1 to 65535 that picks out one service on a machine, such as 22 for SSH or 80 for plain web traffic.
- network layer model — A way of splitting networking into layers (link, network, transport, application) so each layer answers one question and can be tested in order.
- application layer — The top layer, where protocols such as HTTP, DNS and SSH give the bytes meaning as requests, answers and commands.
- OSI model — A seven-layer reference model of networking, where layer 3 is IP addressing, layer 4 is ports and layer 7 is the application protocol.
- load balancer — A server that spreads incoming requests across several copies of a service so no single copy is overloaded.
Taught in
- The Layer Model, As Far As It Earns Its Place — Linux Fundamentals & Systems Administration
- TCP Versus UDP — Linux Fundamentals & Systems Administration
- Load Balancing: Algorithms, Health Checks And Layers — Linux Fundamentals & Systems Administration
- Load Balancing And The Failure Modes It Introduces — Scalable System Design & Distributed Architecture