Service-based state management in Angular - Step-by-Step Execution

Concept Flow - Service-based state management

Component A needs state

↓

Inject Service

↓

Service holds state

↓

Component A reads/updates state

↓

Component B needs same state

↓

Inject same Service

↓

Component B reads updated state

↓

State shared and synced

Components inject a shared service that holds the state. They read and update this state through the service, enabling shared, synced data.

Execution Sample

Angular

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

@Injectable({ providedIn: 'root' })
export class CounterService {
  count = signal(0);
  increment() { this.count.update(c => c + 1); }
}

A service holds a reactive count signal and an increment method to update it.

Execution Table

Step	Action	State Before	State After	Component View Update
1	Component A injects CounterService	count=0	count=0	Displays 0
2	Component A calls increment()	count=0	count=1	Displays 1
3	Component B injects CounterService	count=1	count=1	Displays 1
4	Component B calls increment()	count=1	count=2	Displays 2
5	Component A reads count	count=2	count=2	Displays 2
6	No further updates	count=2	count=2	No change

💡 No more actions; state remains stable at count=2

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
count	0	1	2	2

Key Moments - 3 Insights

Why do both components see the same count value?

Because both inject the same singleton service instance that holds the shared count signal, as shown in steps 3 and 5 of the execution_table.

What happens when increment() is called in one component?

The service updates the count signal, triggering all components using it to update their views, as seen in steps 2 and 4.

Why doesn't the count reset when a new component injects the service?

The service is provided in root, so Angular creates one instance shared across components, preserving state as shown in step 3.

Visual Quiz - 3 Questions

Look at the execution_table at step 4. What is the count value after Component B calls increment()?

A 1

B 2

C 0

D 3

💡 Hint

Check the 'State After' column at step 4 in the execution_table.

At which step does Component A first see the updated count value of 2?

A Step 5

B Step 3

C Step 2

D Step 6

💡 Hint

Look at when Component A reads count after Component B increments it in the execution_table.

If the service was not provided in root but in each component, what would happen to the count values?

A Count value would increment twice as fast

B Both components share the same count value

C Each component has its own count value starting at 0

D Count value would reset to 1 after each increment

💡 Hint

Consider the singleton nature of services provided in root versus component scope.

Concept Snapshot

Service-based state management in Angular:
- Create a service with state (e.g., signal).
- Provide it in root for singleton.
- Inject service in components.
- Components read/update shared state via service.
- State changes reflect in all components using it.

Full Transcript

Service-based state management in Angular means using a shared service to hold and manage state. Components inject this service to read and update the state. Because the service is a singleton provided in root, all components share the same state instance. When one component updates the state, others see the change immediately. This approach keeps state centralized and synchronized across components.