Subject types (Subject, BehaviorSubject, ReplaySubject) in Angular - Performance & Optimization

Performance: Subject types (Subject, BehaviorSubject, ReplaySubject)

MEDIUM IMPACT

This concept affects how efficiently Angular apps handle asynchronous data streams and UI updates, impacting interaction responsiveness and rendering smoothness.

Managing data streams to update UI components efficiently

Angular

const behaviorSubject = new BehaviorSubject(initialValue);
behaviorSubject.subscribe(() => {
  // UI updates with latest cached value immediately
});
behaviorSubject.next(value);

BehaviorSubject caches the latest value, so new subscribers get immediate data, reducing redundant emissions and UI updates.

📈 Performance GainReduces unnecessary re-renders and improves interaction responsiveness by avoiding missed or repeated updates.

Managing data streams to update UI components efficiently

Angular

const subject = new Subject();
subject.subscribe(() => {
  // heavy UI update triggered on every emission
});
subject.next(value);

Subject emits only new values without caching, causing subscribers to miss initial data and triggering multiple UI updates if not managed carefully.

📉 Performance CostTriggers multiple re-renders if subscribers resubscribe frequently; can cause INP delays due to redundant updates.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Subject	Multiple subscriptions trigger repeated DOM updates	Multiple reflows if many emissions	High paint cost due to frequent UI changes	[X] Bad
BehaviorSubject	Single DOM update with cached latest value	Minimal reflows due to fewer emissions	Lower paint cost with controlled updates	[OK] Good
ReplaySubject	DOM updates with replayed values on subscription	Moderate reflows depending on buffer size	Moderate paint cost but consistent UI state	[!] OK

Rendering Pipeline

Subjects emit values that trigger Angular change detection, leading to style calculation, layout, paint, and composite stages. Efficient Subject use minimizes unnecessary change detection cycles and DOM updates.

→Change Detection

→Layout

→Paint

→Composite

⚠️ BottleneckChange Detection and Layout stages are most expensive due to repeated UI updates from frequent emissions.

Core Web Vital Affected

INP

This concept affects how efficiently Angular apps handle asynchronous data streams and UI updates, impacting interaction responsiveness and rendering smoothness.

Optimization Tips

1Use BehaviorSubject to cache and emit the latest value immediately to new subscribers.

2Avoid plain Subject if late subscribers need past data to prevent extra network or computation.

3Use ReplaySubject to replay a fixed number of past values for consistent UI state.

Performance Quiz - 3 Questions

Which Subject type immediately emits the latest value to new subscribers, reducing redundant UI updates?

A Subject

B BehaviorSubject

C ReplaySubject

D AsyncSubject

DevTools: Performance

How to check: Record a session while interacting with components using Subjects. Look for frequent change detection cycles and layout recalculations.

What to look for: High number of change detection events and layout thrashing indicate inefficient Subject usage causing INP delays.

Practice

1. Which type of Subject in Angular immediately sends the last emitted value to new subscribers?

easy

A. AsyncSubject

B. BehaviorSubject

C. ReplaySubject

D. Subject

Solution

1. Step 1: Understand BehaviorSubject behavior

   BehaviorSubject stores the last emitted value and sends it immediately to any new subscriber.

2. Step 2: Compare with other Subjects

   Subject sends only to current subscribers without remembering past values. ReplaySubject replays multiple past values, not just the last one.

3. Final Answer:

   BehaviorSubject -> Option B

4. Quick Check:

   Last value sent immediately = BehaviorSubject [OK]

Hint: BehaviorSubject always sends last value to new subscribers [OK]

Common Mistakes:

• Confusing ReplaySubject with BehaviorSubject
• Thinking Subject remembers past values
• Assuming AsyncSubject behaves like BehaviorSubject

2. Which of the following is the correct way to create a ReplaySubject that stores the last 3 values?

easy

A. new ReplaySubject(1)

B. new ReplaySubject()

C. new ReplaySubject(3)

D. new ReplaySubject('3')

Solution

1. Step 1: Check ReplaySubject constructor

   ReplaySubject takes a number argument specifying how many past values to store and replay.

2. Step 2: Validate options

   new ReplaySubject(3) correctly passes number 3. new ReplaySubject() uses no argument (defaults to unlimited or 1 depending on implementation). new ReplaySubject(1) stores only 1 value. new ReplaySubject('3') passes a string, which is invalid.

3. Final Answer:

   new ReplaySubject(3) -> Option C

4. Quick Check:

   ReplaySubject(3) stores last 3 values [OK]

Hint: ReplaySubject(n) stores last n values for new subscribers [OK]

Common Mistakes:

• Passing string instead of number to ReplaySubject
• Omitting the buffer size argument
• Confusing ReplaySubject with BehaviorSubject constructor

3. Consider this code snippet:

const subject = new BehaviorSubject('start');
subject.next('first');
subject.subscribe(value => console.log('Subscriber 1:', value));
subject.next('second');
subject.subscribe(value => console.log('Subscriber 2:', value));

What will be printed to the console?

medium

A. Subscriber 1: startSubscriber 1: firstSubscriber 1: secondSubscriber 2: second

B. Subscriber 1: firstSubscriber 1: secondSubscriber 2: firstSubscriber 2: second

C. Subscriber 1: firstSubscriber 1: secondSubscriber 2: second

D. Subscriber 1: startSubscriber 1: secondSubscriber 2: startSubscriber 2: second

Solution

1. Step 1: Trace BehaviorSubject emissions

   BehaviorSubject starts with 'start', then next emits 'first'. Subscriber 1 subscribes after 'first', so it receives the last value 'first' immediately, then 'second' when emitted.

2. Step 2: Analyze Subscriber 2 subscription

   Subscriber 2 subscribes after 'second' is emitted, so it immediately receives 'second'.

3. Final Answer:

   Subscriber 1: start
   Subscriber 1: first
   Subscriber 1: second
   Subscriber 2: second -> Option A

4. Quick Check:

   BehaviorSubject sends last value on subscribe [OK]

Hint: BehaviorSubject sends last value immediately on subscribe [OK]

Common Mistakes:

• Assuming Subscriber 2 gets 'first' value
• Ignoring initial 'start' emission to Subscriber 1
• Ignoring immediate emission on subscription

4. What is wrong with this code snippet?

const subject = new Subject();
subject.next('hello');
subject.subscribe(value => console.log(value));

medium

A. The subscription will not receive 'hello' because Subject does not replay past values.

B. The code will throw a syntax error because subscribe is called after next.

C. The Subject should be replaced with BehaviorSubject to avoid errors.

D. The next() method cannot be called before any subscribers exist.

Solution

1. Step 1: Understand Subject behavior

   Subject sends values only to current subscribers. Since next('hello') is called before subscribe, no subscriber receives it.

2. Step 2: Check for errors

   There is no syntax or runtime error. The code runs but subscriber misses the first value.

3. Final Answer:

   The subscription will not receive 'hello' because Subject does not replay past values. -> Option A

4. Quick Check:

   Subject sends only to current subscribers [OK]

Hint: Subject does not replay values to late subscribers [OK]

Common Mistakes:

• Expecting subscriber to get values emitted before subscription
• Thinking next() before subscribe causes error
• Confusing Subject with BehaviorSubject or ReplaySubject

5. You want to create a message service that stores the last 2 messages and sends them to any new subscriber immediately. Which Subject type and setup should you use?

hard

A. Use ReplaySubject(1) and call next() twice to replay last 2 messages.

B. Use BehaviorSubject with initial value and call next() twice to store last 2 messages.

C. Use Subject and manually store last 2 messages in an array to send on subscribe.

D. Use ReplaySubject(2) to store and replay last 2 messages to new subscribers.

Solution

1. Step 1: Identify requirement for storing multiple past messages

   BehaviorSubject stores only the last single value, so it cannot replay two messages automatically.

2. Step 2: Choose Subject type that replays multiple past values

   ReplaySubject with buffer size 2 stores and replays last 2 messages automatically to new subscribers.

3. Step 3: Evaluate other options

   Subject does not store past messages. ReplaySubject(1) stores only one message, not two.

4. Final Answer:

   Use ReplaySubject(2) to store and replay last 2 messages to new subscribers. -> Option D

5. Quick Check:

   ReplaySubject(n) replays last n messages [OK]

Hint: ReplaySubject(n) replays last n messages automatically [OK]

Common Mistakes:

• Using BehaviorSubject to store multiple past messages
• Assuming Subject stores past messages
• Setting ReplaySubject buffer size too low