• Open Daily: 10am - 10pm
    Alley-side Pickup: 10am - 7pm

    3038 Hennepin Ave Minneapolis, MN
    612-822-4611

Open Daily: 10am - 10pm | Alley-side Pickup: 10am - 7pm
3038 Hennepin Ave Minneapolis, MN
612-822-4611
Computer Networking for Developers: Understand TCP/IP, DNS, HTTP, Routing, and Real World Network Failures

Computer Networking for Developers: Understand TCP/IP, DNS, HTTP, Routing, and Real World Network Failures

Paperback

General ComputersProgramming

ISBN13: 9798173442079
Publisher: Independently Published
Published: Sep 11 2026
Pages: 172
Weight: 0.48
Height: 0.43 Width: 6.00 Depth: 9.00
Language: English

Why can perfectly good application code fail simply because one part of the network path behaves differently than expected?

A request that looks like a single function call may depend on DNS resolution, IP addressing, routing, TCP or QUIC, TLS negotiation, proxies, load balancers, cloud networks, containers, timeouts, retries, and remote services. When one layer fails, the application often reports only a vague symptom: timeout, reset, certificate error, 502 response, intermittent connection, or unexplained latency.

Also from

Halstead, Corin

Also in

General Computers