How would you reduce redundant frontend network requests for availability and pricing? Compare batching endpoints, GraphQL, request coalescing/deduplication, HTTP/2 multiplexing, client-side caching with cache keys and TTLs, and pagination/windowing. Provide an example API schema or query, discuss trade-offs (latency, payload size, cacheability, observability), and outline how you would monitor and roll out the change safely.

This question evaluates a candidate's competency in system and API design, frontend performance optimization, caching and request deduplication strategies, and operational observability for reducing redundant network requests for availability and pricing.

How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a hard difficulty System Design question, commonly asked during Onsite rounds at Airbnb.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at Airbnb during technical interviews.

Reduce frontend network requests efficiently

Reduce Redundant Frontend Requests for Availability and Pricing

Context

You are designing the web client and APIs for a bookings marketplace that displays many listings (e.g., 50–200 on search results, plus a detail page). The client repeatedly needs availability and pricing for a user-specified date range and party size. Today it often fires many small, overlapping requests, increasing latency and backend load.

Task

Propose how to reduce redundant frontend network requests specifically for availability and pricing. Compare the following approaches, provide an example API schema or query, discuss trade-offs, and outline safe monitoring and rollout:

Batching endpoints (REST-style)
GraphQL
Request coalescing/deduplication (client and/or server)
HTTP/2 multiplexing
Client-side caching with well-defined cache keys and TTLs
Pagination/windowing of work (e.g., viewport-first)

Include:

An example API schema or query (REST batch and/or GraphQL).
Trade-offs across latency, payload size, cacheability, and observability.
How you would instrument, monitor, and roll out the change safely.

Context

Task

Batching endpoints (REST-style)

GraphQL

Request coalescing/deduplication (client and/or server)

HTTP/2 multiplexing

Client-side caching with well-defined cache keys and TTLs

Pagination/windowing of work (e.g., viewport-first)

Include:

An example API schema or query (REST batch and/or GraphQL).

Trade-offs across latency, payload size, cacheability, and observability.

How you would instrument, monitor, and roll out the change safely.

Reduce frontend network requests efficiently

Quick Overview

Reduce Redundant Frontend Requests for Availability and Pricing

Context

Task

Solution

Submit Your Answer to Earn 20XP

Reduce frontend network requests efficiently

Quick Overview

Reduce Redundant Frontend Requests for Availability and Pricing

Context

Task

Solution

Submit Your Answer to Earn 20XP