Underfetching
Underfetching occurs when an API endpoint returns insufficient data for a view, requiring the frontend to initiate secondary cascading requests to retrieve related details. This creates latency waterfalls (the N+1 request problem), severely slowing down mobile and web application responsiveness.
Technical Architecture & Deep-Dive
Underfetching is common in strict relational REST designs. A client querying `/posts/123` receives only post metadata, requiring additional roundtrips to `/users/45` for the author profile and `/comments?post_id=123` for comments. Over high-latency cellular connections, serial waterfall roundtrips compound latency.
Edge API aggregation eliminates underfetching by querying upstream resources concurrently over high-speed backbone fiber and delivering a unified, composite payload in a single roundtrip to the client.
Key Architectural Benefits
Implement Underfetching at the Edge
Deploy lightweight API aggregation, edge caching, and secret injection in minutes without Docker containers or complex servers.
Frequently Asked Questions
Q:How do edge composers resolve underfetching?
An edge composer queries all required upstream endpoints in parallel from edge Points of Presence, then merges and returns the complete composite data in a single HTTP response.
Related Architecture Concepts
Overfetching occurs when an API response delivers more data than the client application requires to render the current screen or view. For example, downloading an entire 50-field user profile object simply to display an avatar and first name wastes bandwidth, memory, and parsing time.
API Aggregation is the process of combining multiple distinct API calls into a single unified HTTP request. An intermediate edge gateway queries multiple upstream services in parallel, merges the returned data, and delivers a consolidated response to the client, drastically reducing mobile latency and network overhead.
Upstream Fan-out is an execution strategy where an edge gateway dispatches multiple HTTP subrequests to separate origin services concurrently rather than sequentially. The total latency is bound by the single slowest subrequest (max time) rather than the cumulative sum of all subrequests.
Backend for Frontend (BFF) is an architectural pattern where a dedicated gateway layer is created for a specific frontend client (e.g., iOS, Android, React). Instead of clients calling multiple generic backend APIs, the edge BFF aggregates upstream calls, injects credentials, and strips unneeded payload fields before transmission.
Ready-to-Use Edge Recipes
To solve how to combine multiple rest webhooks into one payload, never execute unauthenticated requests or embed private tokens directly in client bundles. RealComposer acts as a sub-10ms edge gateway running on Cloudflare Workers that securely injects credentials from your Secret Vault, normalizes responses, and prevents unauthorized API usage. Route calls through your RealComposer edge URL to guarantee complete privacy, robust origin validation, and low mobile latency.
To solve flutterflow call multiple apis on page load, never execute unauthenticated requests or embed private tokens directly in client bundles. RealComposer acts as a sub-10ms edge gateway running on Cloudflare Workers that securely injects credentials from your Secret Vault, normalizes responses, and prevents unauthorized API usage. Route calls through your RealComposer edge URL to guarantee complete privacy, robust origin validation, and low mobile latency.