Ask almost any frontend developer why they love GraphQL, and you will hear a familiar promise:

"You just ask for the exact fields you need, and the server returns exactly what you asked for. No over-fetching, no under-fetching, no multiple roundtrips."

It sounds like pure sorcery. You write a neat JSON-like query in your frontend codebase:

query GetUserProfile { user ( id : "usr_42" ) { name email posts { title comments { text author { name } } } } }

Enter fullscreen mode

Exit fullscreen mode

You hit send. In a single network request, you get back users, their posts, their comments, and the comment authors, all perfectly nested in a clean JSON object.

Because it feels so seamless from the client side, many developers develop an intuitive mental model: they assume GraphQL is a smart query planner, something like an intelligent SQL optimizer that inspects the request, constructs a series of database joins, and returns the result.

Then the application goes into production.

Traffic ramps up.…