Socket (computing)

Socket (computing)
Name	Socket (computing)
Type	Inter-process communication
Invented	1970s
Os	Unix, Windows, Linux, macOS, BSD

Socket (computing) is an application programming interface abstraction for network communication that enables processes to exchange data across TCP/IP, OSI layers and local inter-process channels. Sockets provide endpoints for sending and receiving data using addressing schemes and protocol stacks implemented by Unix, Windows, and other operating system vendors; they are central to client–server architectures used in World Wide Web services, email systems, and distributed applications.

Overview

Sockets present an endpoint abstraction that maps to underlying TCP, UDP, or other protocol implementations in the IP suite, frequently exposed via an API derived from early Berkeley Software Distribution sockets. Servers bind a socket to an address and listen, while clients create sockets and connect, enabling patterns such as request–response, publish–subscribe, and peer-to-peer communication used by ARPANET, W3C technologies and application frameworks like Apache HTTP Server and NGINX. Sockets interact with networking stacks implemented in kernels from vendors including Linux kernel maintainers, Microsoft, and projects such as FreeBSD.

History and development

The socket API originated in the 1970s and was formalized in the early 1980s by developers of BSD, influenced by work on ARPANET protocols and the TCP/IP suite. Early contributors included researchers at UC Berkeley and standards bodies like IETF, which published RFC documents specifying behavior for TCP and UDP. Subsequent portability efforts led to commercial adoption by Microsoft in Winsock and standardization through the POSIX specifications used by IEEE and the Open Group. Evolution continued with event-driven models introduced by projects such as Sun's Java networking libraries and asynchronous frameworks pioneered in Node.js and libuv.

Types and abstractions

Socket abstractions include stream sockets (reliable, connection-oriented) commonly implemented with TCP, datagram sockets (connectionless) with UDP, and raw sockets providing packet-level access useful for network diagnostics and protocols like ICMP. Other abstractions support domain sockets for local IPC, such as UNIX domain sockets in Linux and BSD, and named pipes in Microsoft Windows. Higher-level socket types and paradigms include secure sockets layered over TLS or SSL used by HTTPS and SMTP over TLS; message-oriented middleware like ZeroMQ and RabbitMQ builds atop socket primitives to provide patterns used in cloud computing and microservices.

API and programming usage

Programmers interact with sockets through APIs such as the BSD socket API, Winsock on Windows, and language-specific bindings in C, C++, Java, Python, Go, Rust, and JavaScript runtimes. Typical API calls include socket creation, bind, listen, accept, connect, send, recv, close, and ioctl or fcntl for I/O control; non-blocking and asynchronous operations use mechanisms like select, poll, epoll in Linux, and kqueue in FreeBSD and OpenBSD. Event-driven frameworks such as libevent, Boost.Asio, and ReactiveX provide abstractions for scalable I/O used by systems like Nginx and HAProxy.

Protocols and addressing

Addressing schemes used by sockets include IPv4 and IPv6 addresses defined by IANA registries, port numbers managed by IANA, and domain sockets referenced by filesystem paths. Socket protocols map to transport and internetworking layers—TCP for reliable byte streams, UDP for datagrams, SCTP for multihoming and message framing—and may encapsulate protocols like HTTP, FTP, SSH, and application protocols standardized by IETF working groups. Name resolution for socket addresses uses services like DNS and may involve mDNS in local networks, while address families like AF_INET and AF_INET6 distinguish IPv4 and IPv6 usage in API calls.

Security and permissions

Socket security covers authentication, encryption, access control, and sandboxing. TLS/SSL libraries such as OpenSSL, GnuTLS, and LibreSSL implement transport security for sockets used by HTTPS and STARTTLS-enabled protocols. Operating system controls like file permissions for UNIX domain sockets, firewall rules in iptables and pf, SELinux policies from Red Hat technologies, and Windows firewall settings govern which processes can bind or connect. Threats include DoS vectors, MITM, port scanning by tools like Nmap, and vulnerabilities mitigated through secure coding standards endorsed by organizations such as Mitre and OWASP.

Implementations and operating system support

Socket implementations are integral to kernels and runtime libraries across Linux, FreeBSD, NetBSD, OpenBSD, macOS, and Windows NT families, with user-space stacks and emulations in projects like lwIP, mTCP, and Wine. Platform-specific APIs include Winsock2 and the POSIX socket interface; platform vendors such as Google and Apple supply transport-layer innovations within mobile stacks for Android and iOS. Large-scale services from Google Cloud, AWS, and Microsoft Azure rely on optimized socket implementations in load balancers, proxies, and orchestration systems like Kubernetes to handle millions of concurrent connections in modern distributed infrastructures.

Category:Computer networking