REST vs GraphQL awareness in Express - When to Use Which

The Big Idea

Discover how one simple change can make your app faster and your code cleaner!

The Scenario

Imagine building a website where users want to see their profile, posts, and comments. You write separate requests for each piece of data, and every time the user clicks, your app asks the server multiple times.

The Problem

Making many separate requests slows down the app and wastes data. Sometimes you get too much data you don't need, or not enough, so you have to ask again. Managing all these requests by hand is confusing and error-prone.

The Solution

REST organizes data into fixed endpoints, but GraphQL lets you ask for exactly what you want in one request. This means faster loading, less wasted data, and simpler code to manage your data needs.

Before vs After

✗ Before

GET /users/123/profile
GET /users/123/posts
GET /users/123/comments

✓ After

POST /graphql
{
  user(id: "123") {
    profile {
      name
      age
    }
    posts {
      title
    }
    comments {
      text
    }
  }
}

What It Enables

It enables building faster, smarter apps that get just the data they need with fewer requests.

Real Life Example

Think of ordering food: REST is like ordering each dish separately, while GraphQL is like telling the chef your whole meal in one order, so everything arrives together and fresh.

Key Takeaways

REST uses fixed URLs for each data type, which can cause many requests.

GraphQL lets you request exactly what you want in one go.

This makes apps faster, simpler, and more efficient.

Practice

1. Which statement best describes the main difference between REST and GraphQL in an Express API?

easy

A. REST uses multiple URLs and HTTP methods; GraphQL uses a single URL with flexible queries.

B. REST uses a single URL and flexible queries; GraphQL uses multiple URLs and HTTP methods.

C. REST and GraphQL both use multiple URLs but differ in data format.

D. REST and GraphQL are identical in how they handle data fetching.

Solution

1. Step 1: Understand REST API structure

   REST APIs use different URLs (endpoints) for different resources and HTTP methods like GET, POST, PUT, DELETE to perform actions.

2. Step 2: Understand GraphQL API structure

   GraphQL uses a single endpoint URL and clients specify exactly what data they want in the query, making it flexible.

3. Final Answer:

   REST uses multiple URLs and HTTP methods; GraphQL uses a single URL with flexible queries. -> Option A

4. Quick Check:

   REST vs GraphQL = multiple URLs vs single URL [OK]

Hint: REST = many URLs; GraphQL = one URL with queries [OK]

Common Mistakes:

• Thinking GraphQL uses multiple URLs like REST
• Confusing HTTP methods usage between REST and GraphQL
• Believing REST and GraphQL are the same

2. Which Express route setup correctly represents a REST API endpoint for getting a user by ID?

easy

A. app.put('/user', (req, res) => { /* fetch user */ });

B. app.post('/user/:id', (req, res) => { /* fetch user */ });

C. app.get('/user/:id', (req, res) => { /* fetch user */ });

D. app.get('/graphql', (req, res) => { /* fetch user */ });

Solution

1. Step 1: Identify correct HTTP method for fetching data

   GET method is used to retrieve data in REST APIs.

2. Step 2: Check URL pattern for resource identification

   /user/:id correctly uses a URL parameter to specify which user to fetch.

3. Final Answer:

   app.get('/user/:id', (req, res) => { /* fetch user */ }); -> Option C

4. Quick Check:

   GET + /user/:id = fetch user [OK]

Hint: GET method + URL with :id fetches resource [OK]

Common Mistakes:

• Using POST instead of GET for fetching data
• Using GraphQL endpoint for REST question
• Using PUT method which is for updates

3. Given this Express GraphQL setup, what will the client receive when querying for { user(id: "1") { name } }?

const { graphqlHTTP } = require('express-graphql');
const schema = buildSchema(`
  type Query {
    user(id: ID!): User
  }
  type User {
    id: ID
    name: String
    email: String
  }
`);
const root = {
  user: ({ id }) => ({ id, name: 'Alice', email: '[e-mail]' })
};
app.use('/graphql', graphqlHTTP({ schema, rootValue: root, graphiql: true }));

medium

A. {"data":{"user":{"id":"1","name":"Alice","email":"[e-mail]"}}}

B. {"data":{"user":{"name":"Alice"}}}

C. {"error":"Field 'user' not found"}

D. {"data":{"user":null}}

Solution

1. Step 1: Understand the GraphQL query

   The query requests only the name field of the user with id "1".

2. Step 2: Check resolver returns full user object

   The resolver returns id, name, and email, but GraphQL returns only requested fields.

3. Final Answer:

   {"data":{"user":{"name":"Alice"}}} -> Option B

4. Quick Check:

   GraphQL returns only requested fields [OK]

Hint: GraphQL returns only requested fields, not full object [OK]

Common Mistakes:

• Expecting all fields returned regardless of query
• Confusing error responses with valid data
• Assuming REST style full object return

4. Identify the error in this Express REST route that causes it to always return an empty response:

app.get('/users/:id', (req, res) => {
  const user = users.find(u => u.id === req.params.id);
  if (user) {
    res.json(user);
  }
  res.end();
});

medium

A. The route path should be '/user/:id' not '/users/:id'.

B. The route should use POST instead of GET.

C. The user lookup uses incorrect comparison operator.

D. res.end() is called even after sending a response, causing empty output.

Solution

1. Step 1: Analyze response flow

   If user is found, res.json(user) sends response, but code continues to res.end() which sends empty response again.

2. Step 2: Understand Express response behavior

   Calling res.end() after res.json() can cause the response to be overwritten or cause errors.

3. Final Answer:

   res.end() is called even after sending a response, causing empty output. -> Option D

4. Quick Check:

   Only send one response per request [OK]

Hint: Send only one response; avoid res.end() after res.json() [OK]

Common Mistakes:

• Using wrong HTTP method for fetching
• Assuming path name causes empty response
• Ignoring that res.end() can overwrite response

5. You want to build an Express API that allows clients to fetch user data with flexible fields and avoid multiple endpoints. Which approach is best and why?

hard

A. Use GraphQL with a single endpoint letting clients specify exactly which fields they want.

B. Use REST but return all fields for every resource to avoid multiple endpoints.

C. Use REST with multiple endpoints for each resource and HTTP methods for actions.

D. Use GraphQL but create multiple endpoints for each query type.

Solution

1. Step 1: Identify requirement for flexible fields and fewer endpoints

   Clients want to specify fields and avoid many URLs.

2. Step 2: Match approach to requirement

   GraphQL uses one endpoint and allows clients to request exactly needed fields, fitting the requirement.

3. Final Answer:

   Use GraphQL with a single endpoint letting clients specify exactly which fields they want. -> Option A

4. Quick Check:

   Flexible fields + single endpoint = GraphQL [OK]

Hint: Flexible data + one URL = GraphQL [OK]

Common Mistakes:

• Choosing REST and returning all fields wastes bandwidth
• Using GraphQL with multiple endpoints defeats its purpose
• Confusing REST flexibility with GraphQL's query power