Field-level cost analysis in GraphQL - Step-by-Step Execution

Concept Flow - Field-level cost analysis

Start Query

↓

Parse Query Fields

↓

Assign Cost to Each Field

↓

Sum Field Costs

↓

Compare Total Cost to Limit

Yes No↓

Reject

↓

Return Result

The query is parsed to identify each field, each field is assigned a cost, costs are summed, and the total is checked against a limit to decide execution.

Execution Sample

GraphQL

query {
  user {
    id
    posts {
      title
      comments {
        text
      }
    }
  }
}

This query requests user id, their posts' titles, and comments' text, each field having a cost contributing to total query cost.

Execution Table

Step	Field	Assigned Cost	Running Total Cost	Action
1	user	1	1	Add cost for 'user' field
2	user.id	1	2	Add cost for 'id' field inside 'user'
3	user.posts	2	4	Add cost for 'posts' field inside 'user'
4	user.posts.title	1	5	Add cost for 'title' field inside 'posts'
5	user.posts.comments	3	8	Add cost for 'comments' field inside 'posts'
6	user.posts.comments.text	1	9	Add cost for 'text' field inside 'comments'
7	Total Cost Check	-	9	Compare total cost 9 to limit 10
8	Decision	-	-	Cost under limit, query allowed

💡 Total cost 9 is less than limit 10, so query execution proceeds.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	Final
total_cost	0	1	2	4	5	8	9	9

Key Moments - 2 Insights

Why does 'user.posts.comments' have a higher cost than 'user.posts.title'?

'user.posts.comments' has cost 3 because nested fields often represent more data or complexity, as shown in execution_table step 5, while 'title' is simpler with cost 1 at step 4.

What happens if total cost exceeds the limit?

As per execution_table step 7 and 8, if total cost was above limit (e.g., >10), the query would be rejected to protect server resources.

Visual Quiz - 3 Questions

Look at the execution_table, what is the running total cost after processing 'user.posts' field?

A 2

B 4

C 5

D 8

💡 Hint

Check the 'Running Total Cost' column at step 3 in execution_table.

At which step does the total cost first exceed 5?

A Step 6

B Step 4

C Step 5

D Step 7

💡 Hint

Look at the 'Running Total Cost' column in execution_table rows for costs above 5.

If the cost of 'user.posts.comments' was reduced from 3 to 1, what would be the final total cost?

A 7

B 8

C 9

D 10

💡 Hint

Subtract 2 from the final total cost 9 shown in variable_tracker.

Concept Snapshot

Field-level cost analysis in GraphQL:
- Assign a cost to each field in the query
- Sum all field costs to get total query cost
- Compare total cost to a predefined limit
- Reject query if cost exceeds limit
- Allows controlling resource use per query

Full Transcript

Field-level cost analysis in GraphQL works by parsing the query to identify each requested field. Each field is assigned a cost based on its complexity or data size. These costs are summed to get the total query cost. This total is then compared to a set limit to decide if the query should be executed or rejected. For example, a query requesting user id, posts, and comments accumulates costs step by step. If the total cost is under the limit, the query runs; otherwise, it is rejected to protect server resources.