application layer
The top layer, where protocols such as HTTP, DNS and SSH give the bytes meaning as requests, answers and commands.
In more detail
Application evidence only exists once the transport connection works. A load balancer or health check at this layer can read requests and check responses, which proves more than an open port. Keep the layers in order when diagnosing.
Related terms
- HTTP — The protocol web browsers and web servers use to send requests and responses.
- DNS — The system that turns names such as learnsome.tech into IP addresses.
- SSH — A protocol for logging in to and running commands on another computer securely over a network.
- 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.
- load balancer health check — A test a load balancer runs against each backend, such as opening a port or requesting a URL, to decide whether it should receive traffic.
- transport layer — The layer that carries data between programs on two machines, identified by port numbers, using TCP or UDP.
- 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