Catalog
concept#Architecture#Software Engineering#Platform#Security

Software-Defined Networking (SDN)

Architectural paradigm separating control and forwarding planes using centralized controllers and programmable interfaces.

Software-Defined Networking (SDN) separates network control from forwarding by using centralized controllers and programmable interfaces.
Established
High

Classification

  • High
  • Technical
  • Architectural
  • Intermediate

Technical context

Orchestration and cloud management platformsMonitoring and telemetry systemsIdentity and policy management services

Principles & goals

Separate control and data planes to simplify changes.Centralized logic with open, standardized interfaces.Programmability and automation as first principles.
Build
Enterprise, Domain, Team

Use cases & scenarios

Compromises

  • Misconfigurations of central controllers can affect wide parts of the network.
  • Lack of standards in some interfaces can lead to vendor lock-in.
  • Insufficient security of control channels creates attack surfaces.
  • Plan controller redundancy and clustered architecture.
  • Use secure channels and authentication for control traffic.
  • Gradual rollout and extensive testing before production.

I/O & resources

  • Network topology and inventory data
  • Security, QoS and SLA requirements
  • Programmable switches or agents on devices
  • Centralized policies and configuration profiles
  • Automated network objects and flows
  • Telemetry data and performance metrics

Description

Software-Defined Networking (SDN) separates network control from forwarding by using centralized controllers and programmable interfaces. It enables dynamic control, automation, and improved visibility across large networks. SDN reduces hardware dependency and supports centralized policy and traffic management for data centers and cloud infrastructures.

✔

  • Increased automation and faster network changes.
  • Improved visibility and centralized policy control.
  • Independence from proprietary hardware functionality.

✖

  • Requires compatible, programmable devices in the data plane.
  • Single-point-of-failure risks without proper controller redundancy.
  • Complexity in operation, security, and interoperability.

  • Time-to-Provision

    Time from request to completed network provisioning.

  • Controller latency

    Delay between control decision and enforcement in the data plane.

  • Fault detection rate

    Speed and accuracy in detecting network anomalies.

Open vSwitch in the Data Plane

Using Open vSwitch for programmable packet forwarding in SDN architectures.

OpenDaylight as a Controller Platform

Controller implementation example for control logic and northbound APIs.

Cloud Provider Virtual Networking

Provider-side use of SDN-like concepts to isolate and automate tenant networks.

1

Inventory and define target SDN use cases.

2

Select and deploy an appropriate controller and agents.

3

Iterative integration, testing and rollout with monitoring.

⚠️ Technical debt & bottlenecks

  • Outdated hardware that does not support programmability.
  • Inconsistent API implementations across devices.
  • Missing automation scripts and infrastructure-as-code.
Controller latency and scalabilityInteroperability with legacy devicesSecure protection of control channels
  • Using SDN controller for small static networks without benefit.
  • Unsecured control channels and unprotected APIs.
  • Migration without adapting operational processes and monitoring.
  • Underestimating operational overhead after deployment.
  • Ignoring controller latency and scaling requirements.
  • Unclear responsibilities between network and DevOps teams.
Network architecture and protocols (OpenFlow, BGP, etc.)Experience with SDN controllers and APIsSecurity and operations knowledge for distributed systems
Requirements for automation and orchestrationNeed for centralized policy and security controlScalability and performance of large networks
  • • Existing hardware must be programmable or replaceable.
  • • Bandwidth and latency requirements can constrain design.
  • • Standards and interfaces must be aligned.