## The Payload Problem

When you use deeply embedded REST APIs to fetch a user profile, the server usually returns a massive 45KB JSON document containing the user's entire history, settings, and metadata. But what if the mobile app only needed to display their `first_name` and `avatar_url` (4KB worth of data)?

### FAQ

**Q: How does GraphQL solve this?**
A: GraphQL allows the client UI to dictate exactly the schema it wants. Instead of the server indiscriminately blasting a massive JSON blob causing severe AWS Egress traffic bills, it executes a surgical query that returns precisely the 4KB requested, cutting bandwidth bills vertically by 90%.