GraphQL vs REST

What you'll walk away with

Explain the core ideas behind GraphQL vs REST
Run the sample GraphQL query or code and verify its output
Apply the technique correctly to the Tutorial Platform and production scenarios

Build the mental model

REST is resource-oriented: each endpoint (`/tutorials`, `/tutorials/42/lessons`) returns a fixed response shape and maps HTTP verbs (GET/POST/PUT/DELETE) to resource state. GraphQL exposes one endpoint (`/graphql`) and lets the client choose the response shape inside the query or mutation string. Its schema is a strongly typed contract, doubling as documentation and a validation layer for both frontend and backend teams.

Connect it to a real scenario

Building the Tutorial Platform's detail page over REST needs three calls: `/tutorials/42`, `/tutorials/42/lessons`, `/authors/7`. Over GraphQL, one query fetches the tutorial, its lessons, and its author in a single nested request. For a simple public catalog list, though, REST's HTTP caching (CDN, browser cache) stays simpler and easier to reason about.

REST maps resources to fixed shapes; GraphQL lets clients shape responses
The schema is a typed contract and documentation
Simple public reads still favor REST's HTTP caching

Try the working example

text

REST                              GraphQL
------------------------------    ------------------------------
GET /tutorials/42                 POST /graphql
GET /tutorials/42/lessons         query { tutorial(id:42) {
GET /authors/7                       title
                                      lessons { title }
(3 round trips)                      author { name }
                                   } }  (1 round trip)

You should see

You can explain the difference between REST and GraphQL and decide which fits a given project.

5-minute try-it

Choose REST or GraphQL for a public marketing site (mostly static list pages) and a complex dashboard (many nested, client-varying views), and justify each choice.

One important caution

Do not force GraphQL to replace REST everywhere. File uploads, simple webhooks, and static-asset caching still fit plain REST/HTTP better.

GraphQL — Thinking in Graphs — GraphQL

Easy traps

Do not force GraphQL to replace REST everywhere. File uploads, simple webhooks, and static-asset caching still fit plain REST/HTTP better.
Validate sample queries and mutations on a local or test server with recoverable data before applying them to production.

Exercise

Choose REST or GraphQL for a public marketing site (mostly static list pages) and a complex dashboard (many nested, client-varying views), and justify each choice.

You'll know it worked when: You can explain the difference between REST and GraphQL and decide which fits a given project.