What is a good default for public read APIs under high traffic?

Problem Statement

Explanation

Public feeds and catalogs often tolerate minor staleness. Use caches and ETag/Last-Modified to cut load and latency. Expose freshness headers so clients know what they got and can retry when needed.

Code Solution

SolutionRead Only

GET /items If-None-Match: "etag123"

Practice Sets

This question appears in the following practice sets:

High-Level Design (HLD) Interview Core

Next Question

Master Interviews
Anywhere, Anytime

What is a good default for public read APIs under high traffic?

Problem Statement

Explanation

Code Solution

Practice Sets

Related Questions

Which statement best describes the Single Responsibility Principle?

Open–Closed Principle encourages what practice when adding features?

High-Level Design (HLD) typically focuses on which artifacts?

Which UML diagram best captures interactions over time between components?

Which pairing describes a healthy design goal?

More from System Design

Master Interviews Anywhere, Anytime

What is a good default for public read APIs under high traffic?

Problem Statement

Explanation

Code Solution

Practice Sets

Related Questions

Which statement best describes the Single Responsibility Principle?

Open–Closed Principle encourages what practice when adding features?

High-Level Design (HLD) typically focuses on which artifacts?

Which UML diagram best captures interactions over time between components?

Which pairing describes a healthy design goal?

More from System Design

Master Interviews
Anywhere, Anytime