1. Client Caching & Data Layer advanced

    A live scoreboard JSON endpoint is cached at the CDN with a 5-second TTL and polled every 5 seconds by each viewer. Peak concurrency for an Indian cricket final is in the range Hotstar publicly reported for the 2019 World Cup semi-final - 25.3 million concurrent viewers. Product wants the payload to include the viewer's own fantasy-team score. Roughly what request rate reaches the origin before and after that change?

    3 min answer cdncache-keyrequest-collapsingpolling
  2. Client Caching & Data Layer advanced

    A quick-commerce app must feel instant while showing inventory that changes constantly. What caching strategy on the client?

    2 min answer zeptoclient-cachestalenessrevalidation
  3. Client Caching & Data Layer intermediate

    A single-page application shows stale data after a user makes a change elsewhere in the product. How should client-side caching and invalidation be designed?

    2 min answer client-cacheinvalidationoptimistic-updatesstaleness
  4. Client Caching & Data Layer beginner

    A user renames their account. The settings page shows the new name at once. The dashboard still shows the old name after a full page navigation and corrects itself only after a hard reload or about 15 minutes. Two different caches are involved. Which is which and which one can application code not invalidate?

    2 min answer http-cachedata-layercache-controletag
  5. Client Caching & Data Layer advanced

    An image discovery application does heavy infinite scrolling with per-user recommendations. What should the client data layer provide?

    1 min answer client-cachingpaginationinvalidationmemory
  6. Client Caching & Data Layer intermediate

    Users complete an action and the interface still shows the previous value until they refresh. Diagnose.

    2 min answer frontendcachinginvalidation