We use analytics cookies.We use cookies to analyze site traffic and improve your experience.
Loading...
System Design and AI Engineering, by Roni Das. 984 interactive lessons.
Start LearningFoundation · Core Fundamentals
The maximum amount of data that can be transferred over a network in a given time. It's the width of the pipe, not how fast the water flows.
In short
Bandwidth is the maximum rate at which data can move across a network connection, measured in bits per second (bps), or more commonly megabits per second (Mbps) and gigabits per second (Gbps). It sets the ceiling on how much data a link can carry, but it does not control how fast a single packet arrives, which is latency.
In short
Bandwidth is the maximum rate at which data can move across a network connection, measured in bits per second (bps), or more commonly megabits per second (Mbps) and gigabits per second (Gbps). It sets the ceiling on how much data a link can carry, but it does not control how fast a single packet arrives, which is latency.
Learn it in the course
This page is the free part.
₹1,111 in India$25 everywhere elseonce, for the whole course
The System Design course covers Bandwidth across a run of lessons, not one page. These 4 alone are about 84 minutes of step-by-step reading, 1 of them with code you run in the browser, all with a quiz.
Maximum data transfer capacity of a network connection.
Reduce data size to save storage and bandwidth, lossless vs lossy, and when each makes sense.
Reduce latency and bandwidth usage, compression, connection pooling, and protocol tuning.
Watching the wires, bandwidth, latency, packet loss, and connectivity between your services.
all part of
System Design Masterclass
770 lessons · about 287 hours · 18 free to read
₹1,111in India, by UPI
$25everywhere else, by PayPal
It is really nice and good Please join the course
You own this course
Continue with Bandwidthpay once,
yours for life
Bandwidth is a capacity number. It tells you the largest amount of data a network path can deliver per unit of time under ideal conditions. A 1 Gbps link can, at best, push one billion bits every second, which is about 125 megabytes per second.
The water-pipe analogy holds up well. Bandwidth is the width of the pipe, not the speed of the water. A wider pipe moves more water at once, but a single drop still takes the same time to travel end to end. That travel time is latency, and it is a separate property.
People mix up bandwidth and speed constantly because internet providers advertise plans in Mbps. A 500 Mbps plan means the link can sustain up to 500 megabits per second of total throughput, not that any one request finishes 500 times faster than a slow connection.
Bandwidth is the theoretical maximum. Throughput is what you actually get after real-world losses: protocol overhead, packet loss, retransmissions, congestion, and shared usage. A 1 Gbps link rarely delivers a full 1 Gbps of useful application data. Achieving 940 Mbps of real throughput on a 1 Gbps Ethernet link is already considered excellent because TCP, IP, and Ethernet headers eat the rest.
Latency is the time for one packet to travel from source to destination, dominated by physical distance and the speed of light in fiber. A satellite link can have huge bandwidth and still feel sluggish because each round trip takes 500 ms or more.
The interaction matters. The bandwidth-delay product (bandwidth multiplied by round-trip latency) tells you how much data is in flight on the wire at any moment. On high-bandwidth, high-latency links this product is large, so TCP needs big window sizes to keep the pipe full. If the window is too small, you never use the bandwidth you paid for.
Bandwidth dominates for bulk transfers: streaming 4K video at 25 Mbps, downloading a 50 GB game, backing up a database to object storage, or replicating data between datacenters. Here you care about total volume, so a wider pipe directly cuts the transfer time.
Bandwidth almost never matters for small, chatty workloads. Loading a typical API response of a few kilobytes is bound by latency and the number of round trips, not bandwidth. Adding more bandwidth to a connection that sends tiny requests gives you nothing.
The practical trade-off in system design is provisioning. Over-provisioning bandwidth wastes money on links and egress fees you never saturate. Under-provisioning causes queuing and packet drops during traffic spikes, which TCP interprets as congestion and backs off, making everything slower. Cloud egress bandwidth is metered and billed, so AWS, GCP, and Azure all charge per gigabyte leaving their network, which makes bandwidth a direct cost line, not just a performance concern.
Netflix recommends roughly 15 to 25 Mbps of sustained bandwidth for a single 4K stream. If a household has a 50 Mbps connection, it can comfortably run two 4K streams at once. A third stream at around 20 Mbps pushes the total to about 60 Mbps, more than the pipe holds, so something starts to buffer or drop to a lower bitrate.
Netflix does not fight this with raw bandwidth alone. It uses adaptive bitrate streaming: the player measures available throughput in real time and switches to a lower-resolution, lower-bitrate version of the same video when bandwidth drops, so playback continues without stalling instead of freezing.
On the supply side, Netflix places its Open Connect caching appliances directly inside ISP networks. This shortens the path and means the high-bandwidth video traffic never has to cross congested internet backbone links, keeping both bandwidth and latency favorable for the viewer.
Netflix Open Connect
Places cache servers inside ISPs so high-bandwidth 4K video never crosses congested backbone links.
AWS
Meters and bills egress bandwidth per gigabyte; Direct Connect offers dedicated links up to 100 Gbps between datacenters and AWS.
Cloudflare
Operates a global network with hundreds of Tbps of total capacity to absorb large traffic and DDoS floods.
YouTube
Uses adaptive bitrate to match stream quality to each viewer's available bandwidth in real time.
No. Bandwidth is the maximum data rate a link can carry, like the width of a pipe. The feeling of speed when loading a page is usually latency and round-trip count, not bandwidth. A higher-bandwidth plan does not make small requests finish faster.
Advertised bandwidth is a theoretical maximum. Real throughput is lower because of protocol overhead from TCP, IP, and Ethernet headers, packet loss and retransmissions, Wi-Fi interference, congestion, and traffic shared with other devices. Getting 90 to 94 percent of the rated number is typical and considered good.
Bandwidth is the maximum possible rate; throughput is the actual useful data rate you measure. Throughput is always less than or equal to bandwidth once you subtract overhead, retransmissions, and congestion losses.
Not directly. Latency is set mostly by physical distance and the speed of light in the medium. Adding bandwidth helps only when a link is congested and packets are queuing; once the pipe has spare capacity, extra bandwidth does nothing for latency.
In bits per second: Mbps for most consumer links, Gbps for datacenter and backbone links. Note that 8 bits make a byte, so a 100 Mbps connection downloads at about 12.5 megabytes per second at best.
Data Compression
Reduce data size to save storage and bandwidth, lossless vs lossy, and when each makes sense
Network Optimization
Reduce latency and bandwidth usage, compression, connection pooling, and protocol tuning
Network Monitoring
Watching the wires, bandwidth, latency, packet loss, and connectivity between your services
Latency
The time delay between sending a request and getting a response. Amazon found every 100ms of extra latency costs 1% in sales.
Throughput
The number of operations a system can handle per unit of time. Think of it as how many cars a highway can move per hour.
CDN
A network of servers distributed globally that caches content close to users. Netflix uses CDNs to stream video from servers near you, not from one central location.
TCP
A reliable transport protocol that guarantees data arrives in order and without errors. It uses a three-way handshake to establish connections.
HTTP
The protocol powering the web. A request-response model where clients ask for resources and servers respond. Stateless by design.
REST API
An architectural style for building APIs using standard HTTP methods (GET, POST, PUT, DELETE). Resources are identified by URLs.
This page explains the idea. The "Bandwidth" lesson builds it up step by step, with diagrams. It is part of the System Design Masterclass course, which has 770 lessons. 18 of them are free to read. You pay once and keep it for life, with no subscription.
Open the Bandwidth lessoncourse 1
From absolute beginner to principal engineer, drawn step by step.
Asked about Bandwidth in an interview?
Each question has why it is asked, a full answer, what the interviewer listens for, the follow-ups, the common mistakes and a diagram (268 diagrams in all). A PDF you keep, junior to staff level.
India: UPI, cards or netbanking through Razorpay. Elsewhere: card or PayPal. Download at once from My packs.
