Why component communication matters in Angular - Performance Evidence

Performance: Why component communication matters

MEDIUM IMPACT

Component communication affects how fast and smoothly data flows between parts of the app, impacting interaction speed and visual updates.

Passing data between Angular components

Angular

Use Angular signals or a shared service with RxJS observables to manage state and communicate efficiently between components.

Limits change detection to only affected components and batches updates, reducing unnecessary work.

📈 Performance GainReduces change detection runs and re-renders, improving interaction responsiveness.

Passing data between Angular components

Angular

Parent component uses multiple EventEmitters and @Input properties with frequent change detection cycles triggering many updates.

Triggers excessive Angular change detection cycles causing slow UI updates and input lag.

📉 Performance CostTriggers multiple re-renders and change detection runs per interaction, increasing INP delay.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
EventEmitters with default change detection	Many DOM updates	Multiple reflows per event	High paint cost due to frequent updates	[X] Bad
Signals or RxJS with OnPush change detection	Minimal DOM updates	Single or no reflows per event	Low paint cost with batched updates	[OK] Good

Rendering Pipeline

Component communication triggers Angular's change detection which leads to style recalculations, layout updates, and painting in the browser.

→Change Detection

→Style Calculation

→Layout

→Paint

⚠️ BottleneckChange Detection is most expensive when many components update unnecessarily.

Core Web Vital Affected

INP

Component communication affects how fast and smoothly data flows between parts of the app, impacting interaction speed and visual updates.

Optimization Tips

1Avoid excessive EventEmitters causing many change detection cycles.

2Use OnPush change detection to limit component updates.

3Leverage signals or RxJS observables for efficient state sharing.

Performance Quiz - 3 Questions

What is the main performance problem with using many EventEmitters for component communication in Angular?

A It causes CSS to reflow unnecessarily.

B It triggers many change detection cycles causing slow UI updates.

C It increases bundle size significantly.

D It blocks network requests.

DevTools: Performance

How to check: Record a performance profile while interacting with components. Look for frequent change detection cycles and layout thrashing.

What to look for: High number of change detection events and long scripting times indicate poor communication patterns.

Practice

1. Why is component communication important in Angular applications?

easy

A. It helps components to load faster independently.

B. It allows components to share data and work together smoothly.

C. It prevents components from being reused.

D. It makes components run without Angular framework.

Solution

1. Step 1: Understand component roles

   Components often need to share data to build a complete UI.

2. Step 2: Recognize communication purpose

   Sharing data helps components work together smoothly and stay in sync.

3. Final Answer:

   It allows components to share data and work together smoothly. -> Option B

4. Quick Check:

   Component communication = sharing data [OK]

Hint: Communication means sharing data between components [OK]

Common Mistakes:

• Thinking components work best completely isolated
• Confusing communication with performance optimization
• Believing Angular runs components without communication

2. Which syntax correctly passes data from a parent to a child component in Angular?

easy

A. <child-comp *data="parentData"></child-comp>

B. <child-comp (data)="parentData"></child-comp>

C. <child-comp #data="parentData"></child-comp>

D. <child-comp [data]="parentData"></child-comp>

Solution

1. Step 1: Identify Angular input binding syntax

   Angular uses square brackets [] to bind data from parent to child.

2. Step 2: Match syntax to data passing

   [data]="parentData" correctly passes parentData to child's @Input() property.

3. Final Answer:

   <child-comp [data]="parentData"></child-comp> -> Option D

4. Quick Check:

   Parent to child uses [property] binding [OK]

Hint: Use square brackets [] for parent to child data [OK]

Common Mistakes:

• Using parentheses () which are for event binding
• Using template reference # incorrectly
• Using structural directive * wrongly

3. Given this parent and child component code, what will be logged when the child emits an event?

Child component TS:
@Output() notify = new EventEmitter<string>();
sendNotification() { this.notify.emit('Hello'); }

Parent component template:
<child-comp (notify)="onNotify($event)"></child-comp>

Parent component TS:
onNotify(message: string) { console.log(message); }

medium

A. Hello

B. undefined

C. Error: notify is not a function

D. No output

Solution

1. Step 1: Understand event emission

   The child emits 'Hello' via notify.emit('Hello').

2. Step 2: Check parent event binding

   The parent listens with (notify)="onNotify($event)", so onNotify receives 'Hello'.

3. Final Answer:

   Hello -> Option A

4. Quick Check:

   Child event emits 'Hello' caught by parent [OK]

Hint: Child emits event, parent listens with (event) binding [OK]

Common Mistakes:

• Confusing @Output with @Input
• Not passing $event in parent handler
• Expecting no output without calling emit

4. What is wrong with this Angular code for passing data from parent to child?

Parent template:
<child-comp data="parentData"></child-comp>

Child component TS:
@Input() data: string;

medium

A. The parent should use parentheses: (data)="parentData".

B. The child should use @Output() instead of @Input().

C. The parent should use square brackets: [data]="parentData".

D. The child should declare data as a function, not a property.

Solution

1. Step 1: Identify correct binding syntax

   Passing data from parent to child requires property binding with square brackets.

2. Step 2: Analyze given code

   Using data="parentData" passes a string literal, not the variable value.

3. Final Answer:

   The parent should use square brackets: [data]="parentData". -> Option C

4. Quick Check:

   Property binding needs [] around attribute [OK]

Hint: Use [] for passing variables, not quotes [OK]

Common Mistakes:

• Using string literals instead of variable binding
• Confusing @Input and @Output decorators
• Using event binding () for data input

5. You have two unrelated Angular components that need to share user login status. Which approach is best to communicate this data?

hard

A. Use a shared service with an observable to hold and broadcast the login status.

B. Pass data directly using @Input() and @Output() between the two components.

C. Use local variables inside each component without communication.

D. Use template reference variables to share data between components.

Solution

1. Step 1: Identify component relationship

   Unrelated components do not have parent-child relation, so @Input/@Output won't work.

2. Step 2: Choose communication method

   A shared service with an observable allows broadcasting data to any component.

3. Final Answer:

   Use a shared service with an observable to hold and broadcast the login status. -> Option A

4. Quick Check:

   Unrelated components communicate via shared service [OK]

Hint: Use shared service for unrelated component communication [OK]

Common Mistakes:

• Trying to use @Input/@Output between unrelated components
• Using local variables that don't share data
• Misusing template reference variables for communication