BehaviorSubject as simple store in Angular - Step-by-Step Execution

Concept Flow - BehaviorSubject as simple store

Create BehaviorSubject with initial value

↓

Subscribe to BehaviorSubject

↓

Component receives current value

↓

Component triggers update

↓

BehaviorSubject emits new value

↓

Subscribers get updated value

↓

UI updates with new data

This flow shows how a BehaviorSubject holds a value, components subscribe to it, and updates flow through the store to the UI.

Execution Sample

Angular

import { BehaviorSubject } from 'rxjs';

const store = new BehaviorSubject(0);

store.subscribe(value => console.log('Value:', value));

store.next(1);
store.next(2);

This code creates a BehaviorSubject store, subscribes to it, and updates the value twice, logging each update.

Execution Table

Step	Action	BehaviorSubject Value	Subscribers Notified	Output
1	Create BehaviorSubject with initial value 0	0	No	No output
2	Subscribe to BehaviorSubject	0	Yes	Value: 0
3	Call next(1) to update value	1	Yes	Value: 1
4	Call next(2) to update value	2	Yes	Value: 2
5	No more updates	2	No	No output

💡 No more updates; BehaviorSubject holds last value 2

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
store.value	0	0	1	2	2

Key Moments - 3 Insights

Why does the subscriber immediately get the initial value when subscribing?

Because BehaviorSubject always emits its current value to new subscribers, as shown in step 2 of the execution_table.

What happens if we call next() multiple times quickly?

Each next() call updates the BehaviorSubject's value and notifies subscribers immediately, as seen in steps 3 and 4.

Does BehaviorSubject lose the last value after updates?

No, it keeps the last emitted value, so new subscribers get the latest state, shown by the value 2 after step 4.

Visual Quiz - 3 Questions

Look at the execution_table, what value does the subscriber receive immediately after subscribing?

A 1

B undefined

C 0

D No value

💡 Hint

Check step 2 in the execution_table where subscription happens and output is 'Value: 0'

At which step does the BehaviorSubject value change to 1?

A Step 3

B Step 2

C Step 4

D Step 5

💡 Hint

Look at the BehaviorSubject Value column in the execution_table for step 3

If we add a new subscriber after step 4, what value will it receive?

A 0

B 2

C 1

D No value

💡 Hint

BehaviorSubject holds the last value; see variable_tracker final value after step 4

Concept Snapshot

BehaviorSubject holds a current value and emits it immediately to new subscribers.
Use next() to update the value and notify all subscribers.
It acts like a simple store for state in Angular apps.
Subscribers always get the latest value on subscription.
Ideal for sharing state reactively across components.

Full Transcript

This visual trace shows how BehaviorSubject works as a simple store in Angular. First, a BehaviorSubject is created with an initial value of 0. When a component subscribes, it immediately receives this current value. Then, when next() is called with new values like 1 and 2, the BehaviorSubject updates its stored value and notifies all subscribers. The subscribers react to these updates, for example by logging the new value. The BehaviorSubject always keeps the last emitted value, so any new subscriber will get the latest state right away. This makes it a great tool for managing shared state reactively in Angular applications.

Practice

1. What is the main purpose of using BehaviorSubject in Angular as a simple store?

easy

A. To hold and share the latest value with all subscribers immediately

B. To perform HTTP requests automatically

C. To create Angular components dynamically

D. To manage routing between pages

Solution

1. Step 1: Understand BehaviorSubject role

   BehaviorSubject holds a current value and shares it with subscribers immediately when they subscribe.

2. Step 2: Compare with other options

   The other options describe unrelated Angular features like HTTP, components, and routing.

3. Final Answer:

   To hold and share the latest value with all subscribers immediately -> Option A

4. Quick Check:

   BehaviorSubject shares latest value immediately [OK]

Hint: BehaviorSubject always gives current value to new subscribers [OK]

Common Mistakes:

• Confusing BehaviorSubject with HTTP or routing
• Thinking it delays value delivery
• Assuming it creates components

2. Which of the following is the correct way to update the value stored in a BehaviorSubject named store$?

easy

A. store$.update(newValue);

B. store$.next(newValue);

C. store$.setValue(newValue);

D. store$.emit(newValue);

Solution

1. Step 1: Recall BehaviorSubject update method

   The method to update a BehaviorSubject's value is next().

2. Step 2: Check other method names

   Methods like update(), setValue(), and emit() do not exist on BehaviorSubject.

3. Final Answer:

   store$.next(newValue); -> Option B

4. Quick Check:

   Use next() to update BehaviorSubject [OK]

Hint: Use next() to push new values to BehaviorSubject [OK]

Common Mistakes:

• Using update() or setValue() instead of next()
• Confusing EventEmitter with BehaviorSubject
• Trying to assign value directly

3. Given this Angular code snippet, what will be logged to the console?

const store$ = new BehaviorSubject(0);
store$.subscribe(value => console.log('Subscriber 1:', value));
store$.next(5);
store$.subscribe(value => console.log('Subscriber 2:', value));
store$.next(10);

medium

A. Subscriber 1: 0
Subscriber 2: 0
Subscriber 1: 5
Subscriber 2: 5
Subscriber 1: 10
Subscriber 2: 10

B. Subscriber 1: 0
Subscriber 1: 5
Subscriber 2: 0
Subscriber 1: 10
Subscriber 2: 10

C. Subscriber 1: 0
Subscriber 1: 5
Subscriber 2: 5
Subscriber 1: 10
Subscriber 2: 10

D. Subscriber 1: 5
Subscriber 2: 5
Subscriber 1: 10
Subscriber 2: 10

Solution

1. Step 1: Trace first subscription

   Subscriber 1 subscribes first and immediately receives initial value 0, then receives 5 after next(5).

2. Step 2: Trace second subscription

   Subscriber 2 subscribes after next(5), so it immediately receives current value 5.

3. Step 3: Trace next(10) call

   Both subscribers receive 10 after next(10).

4. Final Answer:

   Subscriber 1: 0 Subscriber 1: 5 Subscriber 2: 5 Subscriber 1: 10 Subscriber 2: 10 -> Option C

5. Quick Check:

   BehaviorSubject sends current value on subscribe [OK]

Hint: New subscribers get latest value immediately [OK]

Common Mistakes:

• Assuming second subscriber gets initial 0 instead of 5
• Missing initial value emission on subscribe
• Confusing order of console logs

4. Identify the error in this Angular code using BehaviorSubject as a simple store:

const store$ = new BehaviorSubject();
store$.subscribe(value => console.log(value));
store$.next(42);

medium

A. subscribe() must be called with an object, not a function

B. next() cannot be called after subscribe()

C. BehaviorSubject cannot emit numbers

D. BehaviorSubject requires an initial value when created

Solution

1. Step 1: Check BehaviorSubject constructor

   BehaviorSubject requires an initial value passed to its constructor; here it is missing.

2. Step 2: Validate other statements

   Calling next() after subscribe() is valid; subscribe() accepts a function; BehaviorSubject can emit numbers.

3. Final Answer:

   BehaviorSubject requires an initial value when created -> Option D

4. Quick Check:

   BehaviorSubject must have initial value [OK]

Hint: Always provide initial value to BehaviorSubject constructor [OK]

Common Mistakes:

• Omitting initial value in constructor
• Thinking next() can't be called after subscribe()
• Confusing subscribe() argument types

5. You want to create a simple store using BehaviorSubject to hold a user's profile object and update it safely. Which approach correctly updates only the user's name without losing other profile data?

const profile$ = new BehaviorSubject({ name: 'Alice', age: 30 });
// Update name to 'Bob' here

hard

A. profile$.next({ ...profile$.value, name: 'Bob' });

B. profile$.next({ name: 'Bob' });

C. profile$.value.name = 'Bob';

D. profile$.update({ name: 'Bob' });

Solution

1. Step 1: Understand BehaviorSubject value update

   Directly assigning to value property does not notify subscribers; next() must be called with full updated object.

2. Step 2: Preserve existing data while updating name

   Use spread operator to copy existing profile and override name, then call next() with new object.

3. Step 3: Check other options

   profile$.next({ name: 'Bob' }); loses age property; profile$.value.name = 'Bob'; mutates value without notification; profile$.update({ name: 'Bob' }); uses non-existent update() method.

4. Final Answer:

   profile$.next({ ...profile$.value, name: 'Bob' }); -> Option A

5. Quick Check:

   Use next() with spread to update partial data [OK]

Hint: Use spread operator with next() to update partial store data [OK]

Common Mistakes:

• Overwriting entire object losing other properties
• Mutating value directly without next()
• Using non-existent update() method