Inter-Process Communication
Subject: Computer and Technology noun /ˌɪn.tərˈprɑː.sɛs kəˌmjuː.nɪˈkeɪ.ʃən/ 1 definition
- operating-systems
- systems-programming
- distributed-systems
- software-architecture
-
Definition (noun)
Entry #206 · UpdatedInter-Process Communication (IPC) encompasses the operating system mechanisms and protocols that enable independent processes to exchange data and synchronize execution. Because operating systems isolate each process within its own protected virtual address space for fault containment and security, one process cannot directly read or write another's memory the way threads in a single process do. IPC bridges that isolation boundary through explicit channels or controlled memory mappings, balancing throughput, latency, and coupling across local or networked environments.
Common Forms
Pipes and FIFOs: Unidirectional byte streams—anonymous pipes between related processes or named FIFOs backed by filesystem paths—that pass one process's output directly into another's input.
Shared Memory: Memory regions mapped simultaneously into the virtual address spaces of multiple processes, enabling low-latency, zero-copy data exchange when coordinated with semaphores or mutexes.
Message Queues: Kernel-managed buffers that store discrete, ordered messages until consumed, allowing senders and receivers to communicate asynchronously without running at the same pace.
Sockets: Bidirectional endpoints—such as local Unix domain sockets or network TCP/IP sockets—that support both same-host communication and distributed processes across machines.
Example
A web proxy like NGINX accepts incoming HTTPS connections in worker processes and forwards dynamic requests over a local Unix domain socket to an application server pool such as Gunicorn or PHP-FPM. Using a local socket avoids TCP network-stack overhead and enforces filesystem permissions while keeping web-facing workers and application runtimes isolated in separate OS processes.