Why GraphQL Exists

In this lesson, Professor Daniel Martin explains why GraphQL was created and what problems it was designed to solve. Learners compare traditional REST-style API consumption with GraphQL’s client-driven query model, focusing on practical issues such as over-fetching, under-fetching, versioning pressure, mobile performance, and coordination between frontend and backend teams.

The lesson does not yet teach full GraphQL syntax or schema design in depth. Instead, it builds the mental model needed for the rest of the course: GraphQL is a typed contract for asking for exactly the data an application needs, while still giving backend teams control over how that data is resolved.