Why relationships model real data in GraphQL - See It in Action

Modeling Real Data Relationships with GraphQL

📖 Scenario: You are building a simple GraphQL API for a library system. The library has authors and books. Each book is written by one author, and each author can write many books. This relationship models how real-world data is connected.

🎯 Goal: Create GraphQL types to represent Author and Book with a relationship between them. Then write a query to fetch authors and their books, showing how relationships model real data.

📋 What You'll Learn

Create a GraphQL type called Author with fields id (ID!), name (String!), and books ([Book!]!)

Create a GraphQL type called Book with fields id (ID!), title (String!), and author (Author!)

Create a query type with a field authors that returns a list of Author

Write a GraphQL query to fetch all authors with their id, name, and the title of each book they wrote

💡 Why This Matters

🌍 Real World

Modeling relationships like authors and books is common in real databases and APIs. GraphQL lets you express these connections clearly.

💼 Career

Understanding how to model and query related data is essential for backend developers, API designers, and anyone working with databases or GraphQL.

1

Define the Author and Book types

Create GraphQL types called Author and Book. Author should have fields id of type ID! and name of type String!. Book should have fields id of type ID! and title of type String!.

GraphQL

# Define Author and Book types with id and name/title fields

Hint

Start by defining two types with the required fields. Don't add relationships yet.

2

Add relationship fields between Author and Book

Add a field called books to the Author type that returns a list of Book (type [Book!]!). Add a field called author to the Book type that returns an Author (type Author!).

GraphQL

type Author {
  id: ID!
  name: String!
  # Add books field here
}

type Book {
  id: ID!
  title: String!
  # Add author field here
}

Hint

Think about how one author can have many books, and each book has one author.

3

Create the root Query type to fetch authors

Create a Query type with a field called authors that returns a list of Author (type [Author!]!).

GraphQL

type Author {
  id: ID!
  name: String!
  books: [Book!]!
}

type Book {
  id: ID!
  title: String!
  author: Author!
}

# Define Query type here

Hint

The Query type is the entry point for fetching data in GraphQL.

4

Write a GraphQL query to fetch authors and their books

Write a GraphQL query named GetAuthorsWithBooks that fetches all authors with their id, name, and for each book, fetch the title.

GraphQL

# Write the GraphQL query below

Hint

Use nested fields to get books inside authors.

Practice

1. Why do relationships between types in GraphQL help model real-world data?

easy

A. They store data in separate databases automatically.

B. They make the data types run faster in queries.

C. They remove the need for any fields in types.

D. They connect different data types to show how things relate in real life.

Solution

1. Step 1: Understand the purpose of relationships in data

   Relationships link different data types to represent how real-world things connect.

2. Step 2: Identify how GraphQL uses relationships

   GraphQL uses fields in types to show these connections clearly without duplicating data.

3. Final Answer:

   They connect different data types to show how things relate in real life. -> Option D

4. Quick Check:

   Relationships = Real-world connections [OK]

Hint: Think of relationships as real-life links between things [OK]

Common Mistakes:

• Confusing relationships with performance improvements
• Thinking relationships remove fields
• Assuming relationships create separate databases

2. Which of the following is the correct way to define a relationship field in a GraphQL type?

easy

A. type Book { author -> Author }

B. type Book { author = Author }

C. type Book { author: Author }

D. type Book { author: "Author" }

Solution

1. Step 1: Recall GraphQL field syntax

   Fields are defined as fieldName: TypeName without extra symbols or quotes.

2. Step 2: Check each option

   type Book { author: Author } uses correct syntax with colon and type name. Others use invalid symbols or quotes.

3. Final Answer:

   type Book { author: Author } -> Option C

4. Quick Check:

   Field syntax = name: Type [OK]

Hint: Use colon (:) between field and type in GraphQL [OK]

Common Mistakes:

• Using equals (=) instead of colon
• Using arrows (->) instead of colon
• Putting type name in quotes

3. Given the GraphQL types:

type Author { id: ID name: String books: [Book] } type Book { id: ID title: String author: Author }

What will the query <code>{ author(id: "1") { name books { title } } }?

medium

A. Only the list of books without author info

B. Author's name and a list of their books' titles

C. Only the author's name

D. An error because of circular references

Solution

1. Step 1: Analyze the query structure

   The query asks for an author by id, then requests the author's name and their books' titles.

2. Step 2: Understand the relationship fields

   The author type has a books field which is a list of Book types, so nested fields like title can be fetched.

3. Final Answer:

   Author's name and a list of their books' titles -> Option B

4. Quick Check:

   Nested fields return connected data [OK]

Hint: Nested fields fetch related data in one query [OK]

Common Mistakes:

• Thinking circular references cause errors in GraphQL
• Expecting only one level of data returned
• Ignoring nested fields in query

4. Identify the error in this GraphQL type definition:

type User { id: ID name: String posts: Post }

Assuming a user can have many posts, what is wrong?

medium

A. posts field should be a list type, like [Post]

B. posts field should be a scalar type like String

C. posts field should be named postList

D. posts field should be inside a separate type

Solution

1. Step 1: Understand the data relationship

   A user can have many posts, so posts must hold multiple Post objects.

2. Step 2: Check the field type

   The field posts is defined as a single Post, but it should be a list of Post, written as [Post].

3. Final Answer:

   posts field should be a list type, like [Post] -> Option A

4. Quick Check:

   Multiple items = list type [OK]

Hint: Use square brackets [] for lists in GraphQL types [OK]

Common Mistakes:

• Using single type for multiple items
• Changing field name unnecessarily
• Thinking fields must be in separate types

5. You want to model a social network where users can follow many other users. Which GraphQL type definition correctly models this relationship?

hard

A. type User { id: ID name: String followers: [User] following: [User] }

B. type User { id: ID name: String followers: User following: User }

C. type User { id: ID name: String followers: String following: String }

D. type User { id: ID name: String followers: [String] following: [String] }

Solution

1. Step 1: Understand the relationship type

   Users can follow many other users, so followers and following must be lists of User type.

2. Step 2: Check each option's field types

   type User { id: ID name: String followers: [User] following: [User] } correctly uses lists of User for both followers and following. Others use single User or String types incorrectly.

3. Final Answer:

   type User { id: ID name: String followers: [User] following: [User] } -> Option A

4. Quick Check:

   Many-to-many = lists of same type [OK]

Hint: Use lists of the same type for many-to-many relationships [OK]

Common Mistakes:

• Using single User type for multiple followers
• Using String instead of User type
• Confusing field types with scalar lists