StickyPorts

StickyPorts is a network service design pattern used to bind a specific TCP or UDP port to a service instance for the lifetime of that instance. The aim is to provide a stable port identity, reducing churn during restarts and simplifying firewall rules, DNS configuration, and client reachability in dynamic cloud environments.

Operation typically involves a central port registry or service mesh that allocates a fixed port from a reserved range to a running instance and issues a lease. The lease is renewed at intervals; as long as the lease is maintained, traffic directed to the instance on that port reaches the same endpoint. If the lease expires, the port may be released and reassigned, potentially requiring the instance to renegotiate its port binding.

Common use cases include long-lived connections such as chat or streaming, environments with strict firewall or NAT rules that benefit from predictable port numbers, and microservice deployments where stable inbound or outbound ports simplify peer communication and monitoring.

Implementation approaches vary. A service mesh or container orchestrator can act as the port broker, while some deployments use a dedicated port lease service. Security considerations center on access control to the registry, lease integrity, and safeguarding against port exhaustion. Limitations include finite port space, risk of churn during failover, and added complexity in failure detection and recovery.

Status and standards: StickyPorts is not a formal industry standard but appears in vendor-specific features and experimental projects under names like port lease or port affinity. It often complements traditional load balancing and NAT traversal rather than replacing them. See also: port forwarding, sticky sessions, service mesh.