Explain like I'm five · Network

What is Network IPC?

Network IPC, told as a story about opening a dedicated mailbox between distant buildings so they can coordinate.

Building ABuilding Btwo processes in different buildings must coordinateshouting won't reach — the buildings are far apart

Two processes in different buildings must coordinate.Shouting won't reach — the buildings are far apart.

tossing envelopes randomly, some get lost or arrive out of orderwithout a dedicated mailbox between buildings, envelopes get lost and jumbled like this

Tossing envelopes randomly, some get lost or jumbled.Without a dedicated mailbox between buildings, envelopes get lost and jumbled like this.

Building ABuilding Bnetwork IPC = a dedicated mailbox opened between separate buildingsvia sockets or message queues, two processes coordinate even across distant buildings

Network IPC = a dedicated mailbox opened between buildings.Via sockets or message queues, two processes coordinate even across distant buildings.

Sockettalks with the other side live
Message Queuenotes pile up and get picked up later
Port Numberpicks the counter inside the building
TCP/UDPregistered or plain mail
TWO MAILBOX STYLESsocket — talks live, like a phone call (TCP stays connected)message queue — notes pile up, picked up laterport number — tells which counter inside the buildingTCP/UDP — choose registered mail or plain mail

There are two mailbox styles.A socket talks live, like a call; a message queue lets notes pile up for pickup later.

same-building teams just hand envelopes across the hallwaydistant buildings need this dedicated mailbox insteadnetwork IPC is a different story from hand-offs inside one building (local IPC)

Network IPC differs from hand-offs inside one building.Hand-offs between processes on one computer (local IPC) use shared memory or pipes instead.

In one breath

Network IPC = opening a dedicated mailbox (socket, message queue) between processes on separate machines, far apart.

Network-based inter-process communication (IPC) lets processes on different hosts exchange data via sockets or message queues. Unlike local IPC mechanisms such as shared memory or pipes between processes on the same machine, network IPC goes through TCP/UDP and port numbers to reach a remote host.

When grown-ups say it

Socket
A dedicated mailbox for talking with the other side live. Identifies the other side by IP and port.
Message Queue
A mailbox where notes pile up for later pickup. Sender and receiver don't need to be present at once.
Port Number
Which counter inside the building. Distinguishes services at the same address.
TCP/UDP
The registered envelope and the plain one. The two basic shipping methods in this field.
Transport Layer
The stage that handles ports and the registered/plain choice. The very layer network IPC leans on. → the stage that splits ports and picks reliability
Modbus
A simple note rule used on factory floors. One example of a note rule riding on this mailbox. → the note rule where the clerk asks one at a time
Local IPC (OS-level)
The way teams in the same building hand things across the hallway. Those in-building hand-offs are covered in another field (PPE Systems).
Circuit vs Packet Switching
What kind of road the note actually travels. The transport method underneath this dedicated mailbox. → a dedicated road, or splitting it into pieces
Next story
How Carriers Find the Way Among Themselves →
Want another term as a picture book? Request →