Why the network sends pieces, not whole messages
A computer could wait until a long message had crossed the network before sending anything else. Packet switching avoids that bottleneck by chopping data into numbered units, each carrying enough addressing information to travel through the network. At a junction, equipment reads the destination and forwards a packet along an available link; the receiving computer puts the pieces back in order.
The links are shared, rather than reserved for one conversation. A packet from one computer can use a cable, followed by packets from other computers, so a busy connection does not have to sit idle while a single long transfer occupies it. This is especially useful for computer traffic, which often arrives in bursts: a machine may send a short request, pause, then receive a response.
A practical alternative to dedicated circuits
Traditional telephone networks established a continuous circuit for a call. That arrangement works well for a steady voice conversation, but it can waste capacity when computers are silent between bursts. Packet networks instead move data in short turns. If one route becomes congested or unavailable, network equipment can send packets by another route, though they may arrive at different times or out of order.
Packets also make it possible to build a network from separate links and switching machines rather than requiring every pair of computers to have its own direct connection. The tradeoff is extra work: packets need labels, equipment must decide where to send them, and the destination must detect missing pieces and assemble the data. The network’s layers divide up those responsibilities.
From proposal to a working network
In 1965, Welsh physicist Donald Davies proposed using small, standardized packets for computer communication and developed the idea at Britain’s National Physical Laboratory. The NPL team built a packet-switched network, demonstrating how computers could exchange data over shared lines. Davies’s work helped establish a practical model for networking: send data in manageable pieces, let the network route them, and reconstruct the original message at the far end.
That design choice still shapes ordinary internet use. A single web page, call, or file transfer can travel as many separate packets, sharing the same underlying connections with traffic from countless other devices.






