liveBook · Manning

Network stack

A network stack is a layered set of protocols and software or hardware components that enables communication between applications and networked systems.

How 2 Manning books explain it

Latency

A network stack is the software and hardware subsystem that processes network packets across protocol layers between a physical network interface and applications.

How it is used
Identifies network processing within a node as a source of latency and a place to look for avoidable work.
How deep it goes
Traces NIC queues, driver notification, protocol responsibilities, and socket calls, while leaving detailed hardware notification mechanics aside.
Examples
Uses an HTTP request, a NIC-to-application packet-path figure, and connect(), sendmsg(), and recvmsg() calls.
What you can do after
Diagnose/debug with it by tracing where packet processing and deferred transmission can add work to a low-latency application.

Read how Latency explains network stack →

Rust Servers, Services, and Apps

A layered collection of networking protocols and supporting implementations that enables communication between distributed system components.

How it is used
Connects distributed application components and carries web-application communication between servers.
How deep it goes
Defines the stack within a distributed-systems model and identifies HTTP as an application-layer protocol, but does not detail lower layers.
Examples
Uses distributed web applications such as social media, e-commerce, sharing-economy, entertainment, and cloud applications.
What you can do after
Evaluate/understand how distributed web applications place HTTP and server communication within a broader systems stack.

Read how Rust Servers, Services, and Apps explains network stack →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.