Real-time Search with Debounce & Caching
Try the prompt first
Design real-time search with debounced intent, true request cancellation, stale-result suppression, complete cache keys, predictable UI states, and keyboard access.
Constraints
- Keep client, server, and rendering ownership explicit.
- Cover loading, failure, recovery, and accessible interaction states.
Challenge summary
Design responsive search with debounced intent, complete cache identity, real cancellation, and an independent stale-response guard.
What you'll practice
- Separate live input, accepted search intent, request runtime, and result state.
- Build cache keys from query, locale, filters, sort, and permission scope.
- Use AbortSignal to release work while generations protect UI correctness.
- Preserve keyboard selection across loading, refresh, empty, and error states.
- Tune debounce and cache policy from observed behavior rather than fixed rules.
What Premium unlocks
Premium unlocks the request state machine, locale-race worked example, cache contract, accessibility behavior, and measurement plan.
Free related practice
Public interview reports: Blind (March 2022), LeetCode Discuss (July 2024), enginebogie (May 2023), LeetCode Discuss (August 2026) · Meta frontend interview questions · Zalando frontend interview questions · Booking.com frontend interview questions · Agoda frontend interview questions
Upgrade to FrontendAtlas Premium to access this system design scenario. Already upgraded? Sign in to continue.