Subscription lifecycle in GraphQL - Step-by-Step Execution

Concept Flow - Subscription lifecycle

Client subscribes

↓

Server registers subscription

↓

Server listens for events

↓

Event occurs

↓

Server sends data update

↓

Client receives update

↓

Client may unsubscribe

↓

Server cleans up subscription

This flow shows how a client starts a subscription, the server listens and sends updates, and how the subscription ends.

Execution Sample

GraphQL

subscription {
  newMessage {
    id
    content
  }
}

This subscription listens for new messages and receives their id and content when they arrive.

Execution Table

Step	Action	Server State	Client State	Data Sent	Notes
1	Client sends subscription request	Registers subscription for newMessage	Waiting for data	None	Subscription starts
2	Server listens for newMessage events	Listening active	Waiting for data	None	Ready to send updates
3	New message event occurs	Event detected	Waiting for data	None	Event triggers data send
4	Server sends newMessage data	Sends {id:1, content:'Hi'}	Receives data	{id:1, content:'Hi'}	Client gets update
5	Client processes data	Listening active	Data received	{id:1, content:'Hi'}	Client updates UI
6	Client unsubscribes	Removes subscription	Subscription ended	None	Subscription ends
7	Server cleans up resources	No active subscription	Subscription ended	None	Cleanup done

💡 Subscription ends when client unsubscribes and server cleans up

Variable Tracker

Variable	Start	After Step 1	After Step 4	After Step 6	Final
subscriptionActive	false	true	true	false	false
dataReceived	none	none	{id:1, content:'Hi'}	{id:1, content:'Hi'}	{id:1, content:'Hi'}

Key Moments - 3 Insights

Why does the server keep the subscription active after sending data?

Because subscriptions stay open to send future updates until the client unsubscribes, as shown in steps 4 and 5.

What happens if the client never unsubscribes?

The server keeps the subscription active and continues sending updates when events occur, as seen in steps 2 to 5.

When does the server clean up the subscription?

Only after the client unsubscribes, as shown in steps 6 and 7.

Visual Quiz - 3 Questions

Look at the execution table, at which step does the client first receive data?

A Step 5

B Step 2

C Step 4

D Step 6

💡 Hint

Check the 'Data Sent' column in the execution table rows

According to the variable tracker, when does 'subscriptionActive' become false?

A After Step 1

B After Step 6

C After Step 4

D At Start

💡 Hint

Look at the 'subscriptionActive' row values in variable_tracker

If the client never unsubscribes, what would happen to the server state?

A Server keeps listening and sending updates

B Server removes subscription immediately

C Server sends data once then stops

D Server crashes

💡 Hint

Refer to key_moments about subscription lifecycle and server behavior

Concept Snapshot

GraphQL Subscription Lifecycle:
- Client sends subscription request
- Server registers and listens for events
- Server sends data updates on events
- Client receives and processes updates
- Subscription stays open until client unsubscribes
- Server cleans up after unsubscribe

Full Transcript

This visual execution shows the lifecycle of a GraphQL subscription. First, the client sends a subscription request. The server registers this subscription and listens for relevant events. When an event occurs, the server sends data to the client. The client receives and processes this data. The subscription remains active, allowing multiple updates. When the client decides to unsubscribe, the server removes the subscription and cleans up resources. Variables like subscriptionActive track whether the subscription is open. This lifecycle ensures real-time data flow until the client ends it.