Container and presentational components in Angular - Performance & Optimization

Performance: Container and presentational components

MEDIUM IMPACT

This pattern affects rendering speed and responsiveness by separating data logic from UI rendering, reducing unnecessary DOM updates.

Separating data fetching and UI rendering in Angular components

Angular

import { Component, signal, Input } from '@angular/core';

@Component({
  selector: 'app-user-container',
  standalone: true,
  template: `<app-user-presentational [user]="user()"></app-user-presentational>`
})
export class UserContainerComponent {
  user = signal(null);

  constructor() {
    fetch('/api/user')
      .then(res => res.json())
      .then(data => this.user.set(data));
  }
}

@Component({
  selector: 'app-user-presentational',
  standalone: true,
  template: `<div>{{ user?.name }}</div>`
})
export class UserPresentationalComponent {
  @Input() user: any | null = null;
}

Separates data logic from UI, so only presentational component updates when data changes, reducing reflows and improving responsiveness.

📈 Performance GainSingle reflow on data update; faster interaction response; smaller change detection scope.

Separating data fetching and UI rendering in Angular components

Angular

import { Component } from '@angular/core';

@Component({
  selector: 'app-user',
  template: `<div>{{ user?.name }}</div>`
})
export class UserComponent {
  user = null;

  constructor() {
    fetch('/api/user')
      .then(res => res.json())
      .then(data => this.user = data);
  }
}

Combining data fetching and UI rendering causes the component to re-render fully on data change, triggering multiple DOM updates and slowing interaction.

📉 Performance CostTriggers multiple reflows and repaints on data update; blocks interaction until data loads.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Combined data + UI component	High (full component tree updates)	Multiple reflows per data change	High paint cost due to large updates	[X] Bad
Container + presentational components	Low (only presentational updates)	Single reflow per data change	Low paint cost focused on UI parts	[OK] Good

Rendering Pipeline

Container components handle data and state changes, triggering signals or inputs that update presentational components. This limits the scope of style recalculations and layout changes to only the UI parts that need updating.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckLayout due to unnecessary full component re-renders

Core Web Vital Affected

INP

This pattern affects rendering speed and responsiveness by separating data logic from UI rendering, reducing unnecessary DOM updates.

Optimization Tips

1Keep data fetching and state management in container components only.

2Use presentational components to render UI based on inputs or signals.

3Minimize the scope of change detection to improve interaction responsiveness.

Performance Quiz - 3 Questions

What is the main performance benefit of using container and presentational components in Angular?

A Increases bundle size by splitting components

B Reduces unnecessary re-renders by isolating UI updates

C Triggers more reflows due to extra components

D Blocks rendering until all data is fetched

DevTools: Performance

How to check: Record a performance profile while interacting with the component. Look for long tasks or multiple layout recalculations triggered by data updates.

What to look for: Fewer layout recalculations and shorter scripting times indicate better separation and performance.

Practice

1. In Angular, what is the main role of a container component?

easy

A. To manage CSS and animations

B. To display UI elements and styles

C. To define routes and navigation

D. To handle data fetching and business logic

Solution

1. Step 1: Understand container component responsibility

   Container components are designed to manage data and logic, such as fetching data or handling user actions.

2. Step 2: Differentiate from presentational components

   Presentational components focus on showing data and UI, not on data handling.

3. Final Answer:

   To handle data fetching and business logic -> Option D

4. Quick Check:

   Container = data and logic [OK]

Hint: Container = data and logic, Presentational = UI only [OK]

Common Mistakes:

• Confusing container with presentational component roles
• Thinking container manages styles or routes
• Assuming container handles only UI display

2. Which of the following is the correct way to pass data from a container to a presentational component in Angular?

easy

A. Use ngModel in container component only

B. @Input() data: any; in presentational, bind in container template

C. @Output() data: any; in presentational, bind in container template

D. Directly modify presentational component's variables from container

Solution

1. Step 1: Identify Angular data flow syntax

   Data flows from container to presentational via @Input() properties.

2. Step 2: Understand binding in container template

   The container passes data by binding to the presentational component's input property in its template.

3. Final Answer:

   @Input() data: any; in presentational, bind in container template -> Option B

4. Quick Check:

   Data down via @Input() [OK]

Hint: Use @Input() to pass data down from container [OK]

Common Mistakes:

• Using @Output() to pass data down instead of events up
• Trying to modify child variables directly
• Confusing ngModel with input binding

3. Given this Angular container component template:

<app-user-list [users]="userArray" (selectUser)="onUserSelect($event)"></app-user-list>

What is the role of (selectUser) here?

medium

A. It defines a CSS class for styling

B. It binds data from container to presentational component

C. It listens to an event emitted by the presentational component

D. It initializes the component's state

Solution

1. Step 1: Recognize Angular event binding syntax

   Parentheses around selectUser indicate event binding from child to parent.

2. Step 2: Understand event emission from presentational component

   The presentational component emits selectUser event, container listens and runs onUserSelect.

3. Final Answer:

   It listens to an event emitted by the presentational component -> Option C

4. Quick Check:

   Parent listens to child event with (event) [OK]

Hint: Parent uses (event) to listen to child events [OK]

Common Mistakes:

• Thinking (selectUser) passes data down
• Confusing event binding with property binding
• Assuming it styles or initializes state

4. What is wrong with this presentational component code snippet?

@Component({
  selector: 'app-item',
  template: `<div>{{item.name}}</div>`
})
export class ItemComponent {
  item: any;
}

medium

A. Missing @Input() decorator on item property

B. Template syntax is incorrect

C. Selector name is invalid

D. Component class should be abstract

Solution

1. Step 1: Check data input declaration

   The presentational component expects data from parent, so item must be decorated with @Input() to receive it.

2. Step 2: Verify template and selector

   Template syntax and selector are valid; no abstract class needed.

3. Final Answer:

   Missing @Input() decorator on item property -> Option A

4. Quick Check:

   @Input() needed to receive data [OK]

Hint: Add @Input() to receive data in presentational component [OK]

Common Mistakes:

• Forgetting @Input() on input properties
• Thinking template interpolation is wrong
• Assuming selector must be different

5. You want to create a container component that fetches a list of products and passes it to a presentational component for display. Which approach best follows Angular container and presentational component patterns?

hard

A. Container fetches products, stores in a variable, passes via @Input(); presentational only displays list

B. Presentational component fetches products and emits events to container

C. Container and presentational both fetch products independently

D. Presentational component manages fetching and state internally

Solution

1. Step 1: Identify container responsibility

   The container should handle fetching data and managing state.

2. Step 2: Identify presentational responsibility

   The presentational component should only display data received via @Input() without fetching or managing state.

3. Final Answer:

   Container fetches products, stores in a variable, passes via @Input(); presentational only displays list -> Option A

4. Quick Check:

   Container = data fetch, Presentational = display [OK]

Hint: Container fetches data, presentational displays it [OK]

Common Mistakes:

• Letting presentational fetch data
• Duplicating data fetch in both components
• Mixing data logic inside presentational