TransferState for data sharing in Angular - Performance & Optimization

Performance: TransferState for data sharing

MEDIUM IMPACT

TransferState affects the initial page load speed by reducing duplicate HTTP requests between server and client.

Sharing server-fetched data with the client to avoid duplicate HTTP calls

Angular

constructor(private transferState: TransferState, private http: HttpClient) {}

ngOnInit() {
  const saved = this.transferState.get(DATA_KEY, null);
  if (saved !== null) {
    this.data = saved;
    this.transferState.remove(DATA_KEY);
  } else {
    this.http.get('/api/data').subscribe(data => {
      this.data = data;
      this.transferState.set(DATA_KEY, data);
    });
  }
}

Data fetched on server is stored and reused on client, avoiding duplicate HTTP calls and speeding up rendering.

📈 Performance GainReduces client HTTP requests by 1, improving LCP by 200-500ms and lowering server load

Sharing server-fetched data with the client to avoid duplicate HTTP calls

Angular

ngOnInit() {
  this.http.get('/api/data').subscribe(data => this.data = data);
}

This triggers the same HTTP request twice: once on server and again on client, delaying content rendering.

📉 Performance CostBlocks rendering until client HTTP request completes, increasing LCP by 200-500ms depending on network

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Duplicate HTTP fetch on server and client	Minimal	1 reflow after data loads	Medium paint cost due to delayed content	[X] Bad
Using TransferState to share data	Minimal	Single reflow on server render	Lower paint cost due to faster content display	[OK] Good

Rendering Pipeline

TransferState stores server-fetched data in a serialized form embedded in HTML. On client hydration, Angular reads this data to skip redundant HTTP calls, reducing Layout and Paint delays.

→Network

→JavaScript Execution

→Layout

→Paint

⚠️ BottleneckNetwork and JavaScript Execution due to duplicate HTTP requests and data processing

Core Web Vital Affected

LCP

TransferState affects the initial page load speed by reducing duplicate HTTP requests between server and client.

Optimization Tips

1Use TransferState to embed server data for client reuse and avoid duplicate HTTP calls.

2Always remove TransferState data after client reads it to prevent stale data issues.

3Monitor Network tab to ensure API calls are not duplicated on client.

Performance Quiz - 3 Questions

What is the main performance benefit of using TransferState in Angular?

A Avoids duplicate HTTP requests between server and client

B Reduces CSS file size

C Improves JavaScript minification

D Increases DOM node count

DevTools: Network

How to check: Open DevTools Network tab, reload page, and observe if the API call is made twice (server and client) or only once.

What to look for: If the API request appears twice, TransferState is not used properly; a single request means good performance.

Practice

1. What is the main purpose of Angular's TransferState service?

easy

A. To handle routing between Angular modules

B. To share data between server and client to avoid duplicate HTTP requests

C. To store user preferences in local storage

D. To manage component state within a single client session

Solution

1. Step 1: Understand TransferState's role

   TransferState is designed to transfer data fetched on the server to the client to prevent refetching.

2. Step 2: Compare options

   Only To share data between server and client to avoid duplicate HTTP requests correctly describes this purpose; others describe unrelated features.

3. Final Answer:

   To share data between server and client to avoid duplicate HTTP requests -> Option B

4. Quick Check:

   TransferState purpose = share data server-client [OK]

Hint: Remember TransferState avoids duplicate data fetching [OK]

Common Mistakes:

• Confusing TransferState with client-only state management
• Thinking it manages routing or local storage
• Assuming it only works on the client side

2. Which of the following is the correct way to create a state key using makeStateKey in Angular?

easy

A. const KEY = makeStateKey('userData');

B. const KEY = new StateKey('userData');

C. const KEY = createStateKey('userData');

D. const KEY = StateKey('userData');

Solution

1. Step 1: Recall correct syntax for state key creation

   Angular provides the makeStateKey function to create keys, not a constructor or other function.

2. Step 2: Validate options

   Only const KEY = makeStateKey('userData'); uses makeStateKey correctly with proper syntax.

3. Final Answer:

   const KEY = makeStateKey('userData'); -> Option A

4. Quick Check:

   Use makeStateKey() to create keys [OK]

Hint: Use makeStateKey('name') exactly to create keys [OK]

Common Mistakes:

• Using new keyword with StateKey
• Calling non-existent createStateKey function
• Omitting the function call parentheses

3. Given this Angular code snippet on the server:

const USER_KEY = makeStateKey('user');
this.transferState.set(USER_KEY, { name: 'Alice', age: 30 });

What will this.transferState.get(USER_KEY, null) return on the client?

medium

A. null

B. undefined

C. { name: 'Alice', age: 30 }

D. An error because data cannot be retrieved on client

Solution

1. Step 1: Understand data flow with TransferState

   Data set on the server with set is serialized and available on the client.

2. Step 2: Retrieve data on client

   Calling get with the same key returns the stored object, not null or error.

3. Final Answer:

   { name: 'Alice', age: 30 } -> Option C

4. Quick Check:

   Server set data = client get data [OK]

Hint: Data set on server is available on client with same key [OK]

Common Mistakes:

• Expecting null because of second argument
• Thinking data is undefined on client
• Assuming an error occurs when accessing TransferState on client

4. Identify the error in this Angular code using TransferState:

const DATA_KEY = makeStateKey('data');
this.transferState.set(DATA_KEY, { value: 42 });
const data = this.transferState.get('DATA_KEY', null);

medium

A. The key passed to get() should be the StateKey object, not a string

B. The set() method cannot store objects, only strings

C. makeStateKey should not be used for keys

D. transferState cannot be used outside ngOnInit

Solution

1. Step 1: Check key usage in get()

   The get method requires the same StateKey object used in set, not a string.

2. Step 2: Validate other statements

   Objects can be stored, makeStateKey is correct, and transferState can be used anytime in component lifecycle.

3. Final Answer:

   The key passed to get() should be the StateKey object, not a string -> Option A

4. Quick Check:

   Use same StateKey object for set and get [OK]

Hint: Pass StateKey object, not string, to get() [OK]

Common Mistakes:

• Passing string instead of StateKey to get()
• Thinking set() only accepts strings
• Misunderstanding when transferState can be used

5. You want to optimize your Angular Universal app by sharing a list of products fetched on the server with the client using TransferState. Which approach correctly implements this?

hard

A. On client, set products in TransferState and then fetch from server.

B. On client, always fetch products via HTTP and ignore TransferState.

C. On server, store products in a global variable and access it directly on client.

D. On server, fetch products and call transferState.set(PRODUCTS_KEY, products). On client, retrieve with transferState.get(PRODUCTS_KEY, []) before making HTTP call.

Solution

1. Step 1: Understand TransferState usage for server-client data sharing

   Data fetched on server should be stored in TransferState to avoid client refetch.

2. Step 2: Apply correct flow

   On server, fetch products and call transferState.set(PRODUCTS_KEY, products). On client, retrieve with transferState.get(PRODUCTS_KEY, []) before making HTTP call. correctly sets data on server and retrieves on client before HTTP call, optimizing performance.

3. Step 3: Eliminate incorrect options

   Options B, C, and D misuse TransferState or data flow concepts.

4. Final Answer:

   On server, fetch products and call transferState.set(PRODUCTS_KEY, products). On client, retrieve with transferState.get(PRODUCTS_KEY, []) before making HTTP call. -> Option D

5. Quick Check:

   Server sets data, client gets data before HTTP [OK]

Hint: Set on server, get on client before HTTP call [OK]

Common Mistakes:

• Fetching data again on client ignoring TransferState
• Trying to share data via global variables
• Setting data on client instead of server