awesome-everything RU
↑ Back to the climb

Networking & Protocols

Bits on the wire

Crux Voltage, photons, and radio waves carry every byte you send. The speed of light through a medium sets the latency floor nothing above can escape.
Your altitude — climbing toward senior
ZeroJuniorMiddleSenior
You are at junior altitude — the surface
◷ 10 min

You click a link. 200 milliseconds later a page appears in Tokyo. That gap is not servers being slow — it is physics. Every byte your browser sent started as a physical perturbation: voltage on copper, a laser pulse through glass, or a radio wave through air.

What the physical layer actually does

The physical layer has one job: turn bits into a signal, push that signal through a medium, and decode it back to bits on the other side. Every higher layer — IP, TCP, TLS, HTTP — waits for this to happen.

Three media carry virtually all the world’s bits:

  • Copper wire (Ethernet, DSL, USB) — voltage changes on metal conductors.
  • Optical fibre (LAN, submarine cables) — laser pulses through a glass core.
  • Radio (Wi-Fi, 4G/5G, satellite) — modulated electromagnetic waves through air.

Think of any link as a hose. It has two properties: thickness (bandwidth — how many bits per second fit) and length (propagation delay — how long it takes a bit to travel from one end to the other). Every network decision either deals with the hose being too thin, or with the hose being too long.

The latency floor you cannot escape

Light travels at roughly 300,000 km/s in vacuum and about 200,000 km/s in glass fibre (the glass slows it by about 33%). That finite speed creates an absolute floor:

RouteDistanceMinimum one-wayMinimum RTT
NYC → London5,500 km~28 ms~55 ms
NYC → Sydney16,000 km~80 ms~160 ms

Real cables add routing overhead, so the actual RTT NYC → London is 70–90 ms and NYC → Sydney is 200–220 ms. No software, no hardware, no protocol makes a photon travel faster. You can only design around this floor.

Typical link properties
Gig Ethernet
1 Gb/s, 100 m
10G fibre (LR)
10 Gb/s, 10 km
Wi-Fi 6 (5 GHz)
~1 Gb/s @ 5 m
Subsea optical
100+ Tb/s aggregate
Light in glass
~200,000 km/s
NYC → London RTT
70–90 ms

End-to-end journey of a bit

When you click a link, here is what happens at the physical layer:

  1. Your OS hands packet bytes to the network driver.
  2. Your NIC encodes bytes as voltage / light / radio signal.
  3. The signal travels through local cable or Wi-Fi to your router.
  4. Your router decodes back to bytes, processes the IP packet, re-encodes for the WAN uplink — usually fibre going to your ISP.
  5. The ISP’s backbone fibre carries the signal across submarine cables to the destination region.
  6. Destination NIC decodes signal back to bytes; OS delivers to application.

Each hop involves decode → process → re-encode. Long-distance hops use submarine fibre with optical amplifiers (EDFAs) every ~80 km to keep the signal strong without converting to electrical.

Quiz

What physical media carries most long-distance Internet traffic?

Quiz

Why is the New York → Sydney round-trip latency irreducible below ~200 ms?

Why this works

Why CDNs exist. If a user in São Paulo needs content from a server in New York, the physics give a 30 ms one-way floor. A CDN edge node in São Paulo reduces that to 2–3 ms. CDNs do not make the network faster — they shorten the physical path. Same physics, shorter hose.

Order the steps

Order the physical journey of bits from your laptop to a server overseas:

  1. 1 Operating system hands packet bytes to the network driver
  2. 2 Network card encodes bytes as physical signal (voltage, light, or radio)
  3. 3 Signal traverses local cable / fibre / wireless link to your router
  4. 4 Router decodes, re-encodes onto the next link (often a fibre uplink to the ISP)
  5. 5 ISP's fibre carries the signal across submarine cables to the destination region
  6. 6 Destination's network card decodes the signal back into bytes
  7. 7 Destination's operating system delivers the packet to the application

Bandwidth-delay product worked example

1/3
Recall before you leave
  1. 01
    Why doesn't buying more bandwidth reduce page-load latency?
  2. 02
    Light travels at ~200,000 km/s in glass. What is the minimum one-way latency for a 5,500 km transatlantic cable?
  3. 03
    What is the bandwidth-delay product and why does TCP need window scaling for high-BDP paths?
Recap

Every byte travels as a physical signal — voltage on copper, photons through glass, radio waves through air. The medium has two properties: bandwidth (bits per second, set by the cable and modulation scheme) and propagation delay (distance divided by signal speed, ~200,000 km/s in fibre). Higher protocols layer on top but cannot beat these physics: a New-York-to-Sydney request will always take at least ~200 ms round-trip. Practical engineering means knowing the floor numbers: bandwidth-bound problems need more parallelism or compression; latency-bound problems need closer content (CDN) or fewer round-trips (QUIC 0-RTT, TLS resumption).

Connected lessons
appears again in162
Continue the climb ↑Modulation and Shannon
shortcuts expand
search
K
prev piece
k
next piece
j
cycle tier
t
this menu
?
sources4
expand
  1. 01
  2. 02
  3. 03
  4. 04

Trademarks belong to their respective owners. Editorial reference only.