Software-Defined Networking (SDN)
Also known as: network virtualization, programmable networks
Software-Defined Networking (SDN) is a network architecture paradigm that decouples the control plane (routing decisions) from the data plane (packet forwarding). Introduced by McKeown et al. (2008) with OpenFlow, SDN enables network programmability by centralizing control logic in software-based controllers that direct forwarding behavior of simple programmable switches. SDN has transformed network operations, enabling rapid service deployment, traffic engineering, and cloud integration. It is now foundational in data centers and service provider networks.
Read the full method
Sign in with a free account to read this section.
Method map
The neighbourhood of related methods — select a node to explore.
When to use it
Use SDN for data center networks where rapid service deployment and traffic engineering are critical. SDN is beneficial for networks requiring dynamic routing, application-aware policies, or frequent topology changes. Avoid SDN if strict determinism and low latency are required (controller latency adds delays). For small networks or legacy hardware, SDN overhead may not justify benefits. SDN is standard for cloud and large operator networks.
Strengths & limitations
- Programmability: network behavior can be changed by updating software, not hardware
- Centralized control: global view of network simplifies complex policies
- Traffic engineering: dynamic routing responds to congestion and failures in real-time
- Innovation agility: new services can be deployed without hardware upgrades
- Reduced hardware cost: simple switches are cheaper than feature-rich routers
- Integration with cloud: network policies align with VM and container orchestration
- Controller becomes single point of failure; redundancy and synchronization are complex
- Centralized architecture does not scale to very large networks (latency, control overhead)
- Flow table memory (TCAM) is expensive and limited; cannot store all possible flows
- Latency for first packet of a new flow (controller decision time); tail latency can be problematic
- Lack of standardization beyond OpenFlow; interoperability between vendors varies
Frequently asked
What is OpenFlow and how does it relate to SDN?
OpenFlow is a standard protocol for communication between SDN controller and switches. It defines how the controller installs, modifies, and deletes flow rules. OpenFlow enabled vendors to build compatible switches and controllers, accelerating SDN adoption. While OpenFlow is the most deployed SDN southbound protocol, others exist (Netconf, P4).
How does SDN handle failover and redundancy?
SDN controller can be replicated for redundancy; switches connect to multiple controllers with master-slave or consensus protocols. When links fail, controller detects (via topology discovery) and reprograms remaining paths. Failover can be fast (milliseconds) but requires careful design to avoid loops and consistency violations.
What is the control-plane vs. data-plane latency impact?
First packet of a new flow experiences control latency (round-trip time to controller, decision time, flow rule installation): typically 10-100 ms. This can cause slow application startup. Subsequent packets in the same flow use installed rules (sub-microsecond); overall impact depends on flow granularity. Micro-flows worsen control latency.
Can SDN replace traditional routing protocols (BGP, OSPF)?
SDN can implement routing logic in the controller, eliminating the need for distributed protocols. However, this trades distributedness for centralization. Large networks require resilience; full controller dependence is risky. Hybrid approaches (SDN for intra-domain, BGP for interdomain) are practical.
Sources
- McKeown, N., Anderson, T., Balakrishnan, H., et al. (2008). OpenFlow: enabling innovation in campus networks. ACM SIGCOMM Computer Communication Review, 38(2), 69-74. DOI: 10.1145/1355734.1355746 ↗
- Doria, A., Hellstein, H., Haas, R., et al. (2013). Forwarding and Control Element Separation (ForCES) Protocol Specification. RFC 5810. link ↗
How to cite this page
ScholarGate. (2026, June 3). Software-Defined Networking (SDN). ScholarGate. https://scholargate.app/en/telecommunications/software-defined-networking
Which method?
Set this method beside its closest kin and read them side by side — the library lays the books on the table; the choice is yours.
- BGPTelecommunications↔ compare
- MPLSTelecommunications↔ compare
- Network Function VirtualizationTelecommunications↔ compare
- OSPFTelecommunications↔ compare