network function virtualization
/ NFV spelled out: N-F-V /
For decades, each job a network does to traffic in the middle — a firewall, a load balancer, a VPN gateway, a traffic shaper — came as its own dedicated appliance: a purpose-built box you bought, racked, cabled, and replaced when you needed more capacity. It is a bit like having a separate single-purpose kitchen gadget for every task. Network function virtualization is the move away from that: instead of dedicated hardware, you run each of those functions as software on ordinary commodity servers, the same general-purpose machines you would use for any cloud workload.
Concretely, NFV takes a network function that used to live in a specialized middlebox and packages it as software — a virtual network function, or VNF — running in a virtual machine or container on a standard server. A firewall becomes a firewall program; a load balancer becomes a load-balancer program. Because they are just software, you can spin up more instances when traffic rises, tear them down when it falls, move them between data centres, and upgrade them by deploying new code. An orchestration system manages their lifecycle (where to place each VNF, how many to run, how to connect them), and several VNFs can be strung together so traffic passes through them in order — service chaining.
Why it matters: NFV decouples network functions from proprietary hardware, which can cut cost, speed up deployment, and add elasticity — the same forces that made cloud computing attractive, applied to the network's middle. It pairs naturally with SDN: SDN programs how traffic is steered, NFV provides the software functions to steer it through. Be honest about the trade-offs, though: software on general-purpose CPUs is usually slower and less efficient per packet than purpose-built silicon, so high-throughput VNFs need careful engineering (fast packet I/O, hardware offload) to keep up, and you trade simple dedicated boxes for a more complex software system to operate.
A company used to buy a hardware firewall appliance for each new office. With NFV, it instead runs firewall software as a VNF on the commodity servers it already owns. When a branch's traffic doubles, it launches a second firewall instance in minutes instead of shipping and installing another box — and when the spike passes, it shuts the extra instance down.
Network functions become software you can scale up and down, not boxes you must buy.
NFV (functions as software on commodity servers) and SDN (programmable, centralized control of forwarding) are distinct ideas that are often used together but neither requires the other. A common mistake is to treat them as the same thing.