GraphQL fixes REST API over

Short summary

This lesson explores over-fetching and under-fetching, two critical REST API problems that mobile developers face in production. Over-fetching occurs when endpoints return more data fields than the UI needs; GraphQL solves this by letting clients select only required fields. Under-fetching happens when a single endpoint can't satisfy a view's data needs, requiring multiple requests; GraphQL unifies multiple resource requests into one, reducing client-side orchestration complexity.

• •Over-fetching wastes bandwidth by sending unused data fields to mobile clients on limited connections
• •GraphQL lets clients specify exactly which fields they need, eliminating wasted data transfer
• •Under-fetching forces multiple network round-trips; GraphQL bundles multiple resource requests into one unified query

Generated with AI, which can make mistakes.