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
81

Frontend System Design · Lesson 81 of 86 · 4 min

Interactive, Responsive Data Visualizations

This is where you connect theory to practice, showing you can build visualizations that don't just look good, but also perform under pressure from user interaction and device constraints.

Handling User Input Without Freezing the UI

Any interaction on a large dataset—hovering, dragging, typing in a filter—can trigger expensive re-renders or data processing. If you run these operations synchronously on every event, you'll block the main thread and freeze the UI. The goal is to stay within the ~16ms frame budget.

The two primary tools for this are debouncing and throttling. They are not interchangeable.

  • Debounce: Use for discrete actions that signal the end of a user's input. Think of a search bar: you only want to fire the query after the user has stopped typing for a moment.
  • Throttle: Use for continuous events where you need periodic updates. Think of dragging a selection box or panning a map: you want to provide visual feedback during the action, but not for every single pixel moved.

The trap: A common mistake is implementing a debounce that doesn't clear the previous timer. This leads to a cascade of delayed function calls instead of a single one. Always clearTimeout before setting a new one.

function debounce<T extends any[]>(
  func: (...args: T) => void,
  delay: number
): (...args: T) => void {
  let timeoutId: ReturnType<typeof setTimeout> | null = null;

  return function(this: any, ...args: T) {
    if (timeoutId) {
      clearTimeout(timeoutId);
    }
    timeoutId = setTimeout(() => {
      func.apply(this, args);
    }, delay);
  };
}

This flow is critical to explain.

Adapting the Visualization to its Container

A responsive visualization adapts its layout and density to the available space. It's not just about making it smaller; it's about maintaining clarity.

For SVG, the viewBox attribute is the simplest way to achieve proportional scaling. Define your chart in a fixed coordinate system (e.g., 0-1000 wide, 0-600 high), set the viewBox to "0 0 1000 600", and the browser handles the rest. The SVG scales like an image, preserving its aspect ratio.

For Canvas, you have to do the work yourself. On resize, you must update the canvas element's width and height attributes, clear it, and redraw everything based on the new dimensions.

To detect size changes, use a ResizeObserver. It's more efficient and reliable than listening to the global window.resize event, as it targets a specific element and fires only when that element's dimensions actually change.

In an interview, talking about ResizeObserver over window.resize shows you understand modern browser APIs and think about component encapsulation. A chart component shouldn't depend on the global window if it only cares about its own container.

Progressive Rendering and Level of Detail

You cannot render a million points on a 400px-wide chart. Even if you could, the result would be an unreadable blob of overplotting. The solution is to adapt the data, not just the layout, to the viewport and zoom level. This is called progressive rendering or Level of Detail (LOD).

The strategy depends on the zoom level:

  • Zoomed out (low detail): Don't render individual points. Instead, show an aggregated view like a heatmap, or render a small, random sample of the data (e.g., 1% of points).
  • Zoomed in (high detail): As the user zooms into a specific region, query and render the actual data points that fall within that bounding box.

This requires a data structure or backend that can be queried spatially.

Client-side or server-side? For datasets up to a few hundred thousand points, a client-side spatial index like a quadtree can be fast enough. You load the data once and query it locally. For millions or billions of points, this must be a server-side concern. The client sends the current viewport (bounding box, zoom level) to an API, which returns only the aggregated or sampled data needed for that view.

Offloading Work to a Web Worker

Sometimes, even with debouncing, the data processing task is too heavy for the main thread. Calculating a complex layout, filtering a massive in-memory array, or parsing a large file will still cause jank.

This is the exact use case for a Web Worker. Move the heavy computation to a background thread. The main thread sends the worker a message with the raw data and parameters, and the worker sends a message back with the results.

This isn't a silver bullet. There's overhead in serializing data to send it between threads (postMessage). It's best for CPU-bound tasks that take more than 50-100ms. For quick operations, the overhead might make it slower. The key benefit is keeping the UI responsive while the work is being done.

Try it

Find a component in a personal project that filters a list based on a text input. Add a debounce utility like the one above and apply it to the onChange handler. Log the search term to the console inside the debounced function to see how it only fires after you stop typing.

Next: We'll look at how to get the data in the first place in "Data Fetching and Aggregation for Dashboards".

Lock it in — apply this lesson under interview conditions.

Try a free mock interviewPractice system design problems
Previous

Rendering Large Datasets: Canvas vs SVG

Next

Data Fetching and Aggregation for Dashboards