Frontend School
DashboardProblemsLearnPracticeMock InterviewReportsStatsBuy Credits
DashboardProblemsLearnPracticeMock Interview
Frontend System Design Roadmap
  1. 1.HTTP/1.1 vs HTTP/2 vs HTTP/3 (QUIC)
  2. 2.TCP and TLS Handshakes: Connection Setup Costs
  3. 3.Browser Network Stack and Connection Pooling
  4. 4.GET vs POST and Idempotency in HTTP
  5. 5.The Critical Rendering Path (CRP)
  6. 6.DOM, CSSOM and the Render Tree
  7. 7.Layout, Paint and Compositing
  8. 8.Reflows and Repaints Explained
  9. 9.Event Loop: Call Stack, Task and Microtask Queues
  10. 10.Async JavaScript: Promises and async/await
  11. 11.Web Workers: Multi-threading in the Browser
  12. 12.Browser Storage: Cookies, Web Storage, IndexedDB
  13. 13.Client-Side Storage: Limits and Security Risks
  14. 14.Choosing the Right Client-Side Storage
  15. 15.HTTP Caching: Cache-Control, ETag, Last-Modified
  16. 16.Browser-Level Caching Mechanisms
  17. 17.Cache Invalidation for Frontend Apps
  18. 18.Structuring a Large Single-Page App
  19. 19.Component-Based Architecture Principles
  20. 20.Props, State and Component Lifecycle
  21. 21.Module Bundling Basics
  22. 22.Core Web Vitals: LCP, INP and CLS
  23. 23.FCP and Time to Interactive (TTI) Explained
  24. 24.Measuring Performance: Lighthouse and WebPageTest
  25. 25.Asset Compression and Minification Basics
  26. 26.What Is a CDN and How Does It Work?
  27. 27.CDN Benefits: Latency, Availability, Offload
  28. 28.CDN Cache Behavior and Invalidation
  29. 29.Global State vs Local Component State
  30. 30.State Patterns: Redux, Zustand and Context
  31. 31.Data Fetching: React Query and SWR
  32. 32.Immutable Data in Frontend State
  33. 33.SSR vs CSR: Rendering Trade-offs
  34. 34.Hydration and Time to First Byte (TTFB)
  35. 35.Static Site Generation (SSG) for Speed and SEO
  36. 36.Incremental Static Regeneration (ISR)
  37. 37.Micro-Frontends: Core Principles
  38. 38.Micro-Frontend Integration Strategies
  39. 39.Communication Between Micro-Frontends
  40. 40.Micro-Frontends: Pros and Cons for Large Teams
  41. 41.Real-Time: Polling, SSE and WebSockets
  42. 42.Real-Time Use Cases: Chat, Alerts, Live Data
  43. 43.Designing a Real-Time Data Flow
  44. 44.Scaling WebSocket Connections
  45. 45.Responsive Images: srcset, sizes and picture
  46. 46.Modern Image Formats: WebP, AVIF, JPEG XL
  47. 47.Lazy Loading Images and Videos
  48. 48.Video Streaming: HLS, DASH, Adaptive Bitrate
  49. 49.REST and GraphQL for Frontend Engineers
  50. 50.Batching, Throttling and Debouncing API Calls
  51. 51.Handling API Errors in the Frontend
  52. 52.Authentication Flows: OAuth and JWT
  53. 53.Global Error Boundaries in React
  54. 54.Error Reporting: Sentry and LogRocket
  55. 55.Graceful Degradation and Fallback UIs
  56. 56.Real User Monitoring (RUM)
  57. 57.CORS: Cross-Origin Resource Sharing
  58. 58.Preventing XSS (Cross-Site Scripting)
  59. 59.CSRF Protection for Frontend Apps
  60. 60.Content Security Policy (CSP)
  61. 61.Storing Auth Tokens: Cookies vs localStorage
  62. 62.PWA Manifest and Installability
  63. 63.Service Workers: Lifecycle and Caching Strategies
  64. 64.Offline Support and Background Sync
  65. 65.Push Notifications for Web Apps
  66. 66.Webpack vs Vite vs Parcel
  67. 67.Code Splitting, Tree Shaking, Asset Optimization
  68. 68.Module Resolution and Hot Module Replacement
  69. 69.Monorepo Tooling: Nx and Lerna
  70. 70.Atomic Design for Component Libraries
  71. 71.Theming and Customization in Design Systems
  72. 72.Accessibility in Component Libraries
  73. 73.Component Library Docs, Testing and Versioning
  74. 74.Publishing and Consuming a Component Library
  75. 75.Full-Text Search: Levenshtein and Fuzzy Matching
  76. 76.Indexing Large Datasets in the Browser
  77. 77.Search Performance: Debouncing and Web Workers
  78. 78.Integrating Backend Search Services
  79. 79.Choosing a Chart Library: D3, Chart.js, Recharts
  80. 80.Rendering Large Datasets: Canvas vs SVG
  81. 81.Interactive, Responsive Data Visualizations
  82. 82.Data Fetching and Aggregation for Dashboards
  83. 83.A/B Test Design and Rollout Strategies
  84. 84.Client-Side vs Server-Side A/B Testing
  85. 85.Feature Flags and Remote Configuration
  86. 86.Experiment Data Collection and Analytics
Frontend System Design Roadmap
27

Frontend System Design · Lesson 27 of 86 · 4 min

CDN Benefits: Latency, Availability, Offload

In a system design interview, you justify using a CDN with these three specific benefits. Know them cold.

When you propose using a CDN, you're not just adding a box to a diagram. You are making a specific engineering trade-off to improve performance and reliability. You need to articulate precisely what you gain. The three core benefits are lower latency, higher availability, and reduced load on your origin server.

Reduce Latency by Serving Closer to the User

The speed of light is a hard limit. The farther your user is from your server, the higher the latency. A CDN shortens this distance by caching your assets on servers (Points of Presence, or PoPs) around the world.

When a user in Sydney requests a JavaScript bundle from your origin server in Virginia, the request has to cross the Pacific and back. The round-trip time (RTT) alone could be 150-200ms. If that asset is instead served from a CDN PoP in Sydney, the RTT drops to under 20ms.

This has a direct, measurable impact on Core Web Vitals. Lower latency for critical CSS and JavaScript files improves First Contentful Paint (FCP) and Largest Contentful Paint (LCP). Faster asset loading means your app becomes interactive sooner.

In an interview, don't just say "it makes the site faster." Say: "By placing assets on edge servers closer to the user, we reduce network RTT. This directly improves our LCP and FCP metrics, especially for our global user base."

Increase Availability Through Redundancy

A CDN is a massively distributed system. This inherent redundancy makes your application more resilient.

If a single CDN edge server fails, traffic is automatically rerouted to the next nearest healthy one. The user might experience a slightly higher latency for one or two requests, but the site stays up. This is far better than your single origin server going down and taking the entire application with it.

Most major CDNs also provide protection against Distributed Denial of Service (DDoS) attacks. They can absorb huge volumes of malicious traffic at the edge, preventing it from ever reaching and overwhelming your origin server. This is a critical availability feature that's nearly impossible to build yourself.

The trap: Don't assume a CDN makes your application fully available if the origin goes down. If the CDN has a cache miss for a critical asset, and your origin is offline, the request will fail. A CDN primarily improves availability for cached static assets. Dynamic API calls will still fail.

Offload the Origin to Cut Costs and Handle Scale

Every request for a static asset that a CDN handles is a request your origin server doesn't have to. This is called origin offload.

For static assets like images, CSS, and JS bundles, you can achieve cache hit ratios of 95% or higher. This means only 5% of requests for those assets ever reach your server. This drastically reduces the load, bandwidth, and compute costs for your origin infrastructure.

It also frees up your origin servers to do what they're best at: handling dynamic, non-cacheable requests like API calls and server-side rendering. By offloading the "dumb" work of serving static files to the CDN, you allow your core application logic to perform better under load.

This is the flow:

How to Configure Your Frontend Build for a CDN

You don't just "turn on" a CDN. Your frontend build process needs to know where to point for assets. The most common way to do this is by configuring a publicPath in your bundler.

This tells your build tool (like Webpack or Vite) to prepend a specific URL to all your generated asset paths.

Here’s a typical Webpack configuration:

// webpack.config.js
import path from 'path';
import { Configuration } from 'webpack';

const config: Configuration = {
  mode: 'production',
  entry: './src/index.ts',
  output: {
    // This is the key part.
    // All generated asset URLs will start with this prefix.
    publicPath: 'https://cdn.example.com/assets/',
    
    // Using [contenthash] is critical for cache busting.
    // When a file's content changes, its name changes, forcing a new download.
    filename: '[name].[contenthash].js',
    path: path.resolve(__dirname, 'dist'),
    clean: true,
  },
  // ... other configs like modules, plugins, etc.
};

export default config;

When you build, your index.html will contain tags like <script src="https://cdn.example.com/assets/main.a1b2c3d4.js"></script>. The browser will fetch the script directly from the CDN, not your origin server.

The trap: Serving assets from a different domain (cdn.example.com) than your main site (www.example.com) can cause Cross-Origin Resource Sharing (CORS) errors. This is especially common with web fonts or when fetching assets via JavaScript. You must configure your CDN to send the correct Access-Control-Allow-Origin HTTP header to avoid this.

Try it

Open your browser's dev tools on a major site like stripe.com or theverge.com. In the Network tab, find a static asset (a JS, CSS, or image file). Inspect its response headers. Can you identify which CDN served it (look for headers like Server, X-Served-By, or cf-ray) and whether it was a cache hit (look for X-Cache, cf-cache-status, or similar)?

Next: We'll cover how CDNs decide what to cache and for how long in CDN Cache Behavior and Invalidation.

Lock it in — apply this lesson under interview conditions.

Try a free mock interviewPractice system design problems
Previous

What Is a CDN and How Does It Work?

Next

CDN Cache Behavior and Invalidation