bandwidth
How much data a network connection can carry per second, and by extension the amount of data a request or response uses up.
In more detail
It is measured in bits per second, such as 100 megabits per second. Caching, compression and smaller payloads save bandwidth, which lowers costs and speeds up slow connections.
Examples
2 TB = 16,000 gigabits; at 1 Gbit/s that is about 4.4 hours of copyingcopy_h = DATA_TB * 8000 / LINK_GBPS / 3600In the browser: Bandwidth is capacity, while latency is delay. Cookies sent on every request, unused preloads and double downloads all spend bandwidth that users on slow or metered connections cannot spare.Related terms
- cache validation — Asking the server whether a stored response is still current by sending back its validator, such as an ETag, in a conditional request.
- bytes, kilobytes, megabytes — Units of data size: a kilobyte is about a thousand bytes, a megabyte about a million, a gigabyte about a billion.
- egress — Network traffic leaving a system or network, as opposed to ingress traffic coming in.
- bits per second — The unit for network speed and bandwidth, counting individual bits rather than bytes.
- CDN — A network of servers near users that keep copies of public content, such as images, and serve them quickly.
- latency — The time between asking for something and getting the answer back.
- recovery site — An alternative location where an organisation can run its critical systems and carry on working if its main site becomes unusable.
- RTO — Recovery time objective: how long the business can accept a service being down before it is restored.
- preload — A resource hint, <link rel="preload">, that makes the browser download a file needed for the current page right away at high priority.
- cookie — A small named value a server asks a browser to store and send back automatically on later matching requests.
- responsive images — Offering several sizes of the same image so each device downloads the smallest one that still looks sharp.
- compression — Encoding data in fewer bytes by removing repetition, so it takes less space and less time to send.
Taught in
- Caching And Conditional Requests — Modern API Architecture: REST, GraphQL & gRPC
- The Estimate That Copied The Rack — AWS Certified Cloud Practitioner (CLF-C02) Exam Prep
- Storage Performance: IOPS, Throughput And The Right Volume — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Network Performance: Peering, Transit Gateway And The Edge — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- The Performance Clinic: Five Slow Systems, Five Fixes — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Network Cost: NAT Gateways, Zones And Data Out — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Post-Quantum Cryptography & Key Lifecycles — Cybersecurity Fundamentals, GRC & Cryptography
- Business Impact Analysis, RTO & RPO Modeling — Cybersecurity Fundamentals, GRC & Cryptography
- Disaster Recovery Sites: Hot, Warm & Cold — Cybersecurity Fundamentals, GRC & Cryptography
- Critical Rendering Path: Preload, Prefetch And Scripts — Frontend Architecture & Web Platform
- Client Storage Paradigms: Cookies, Storage Tradeoffs — Frontend Architecture & Web Platform
- Image & Font Optimization: Zero Layout Shift Assets — Next.js 15 & Modern App Router Architecture
- Script Optimization: next/script & Lazy Third Parties — Next.js 15 & Modern App Router Architecture
- Native Compression: node:zlib & Streaming Codecs — Node.js Internals & Backend Services
- Stream Pipelines: pipeline, AbortSignal & Teardown — Node.js Internals & Backend Services
- Native HTTP/2 Protocols: Multiplexed Streams & Push — Node.js Internals & Backend Services
- Back Of The Envelope Estimation: Storage And Bandwidth — Scalable System Design & Distributed Architecture
- Worked Design Three: A Metrics Ingestion Pipeline — Scalable System Design & Distributed Architecture
- A Card With No Driver, A Stick With Too Much: Devices And Kernel Modules — CompTIA Linux+ (XK0-006) Exam Prep