State Management in Modern Front-End Frameworks (React, Vue, Angular)

Rajesh Gami

Modern front-end applications have grown significantly in scale and complexity. What started as small browser-side scripts has now evolved into complex, feature-rich platforms that mirror the sophistication of backend systems. As applications grow, the biggest challenge developers face is controlling the flow of data. Unpredictable data flows lead to bugs, inconsistent UI, performance issues, and maintainability problems.

In this article, we will explore how front-end state management works in React, Vue, and Angular. We will also compare how these frameworks approach state handling, and then go deeper into how to implement state management in Angular the right way.

This article is written for senior developers who need clarity, depth, and real-world guidance.

1. Why State Management Matters

Every modern web application deals with multiple categories of state:

Local UI state
Things like showing a modal, controlling form fields, toggling sidebars.
Global application state
User session, permissions, API results, application configuration.
Server cache and async state
Data from HTTP calls, caching, revalidation, optimistic updates.
URL and router state
Filters, sorting, params, navigation.
Derived or computed state
Values that depend on other pieces of state, such as total cart value.

When your application has all these layers, you must have a clear strategy for how state flows. Without a good strategy:

Components start sharing too much logic.
Multiple parts of the application begin duplicating state.
Bugs appear because two parts of the UI are out of sync.
Async behavior (like loading or retrying) becomes unpredictable.
Unit testing becomes hard.
Refactoring becomes slow.

Good state management aims to solve these problems by creating predictable state flows, clean separation of responsibilities, and clarity in how your data behaves.

2. Approaches to State Management

State management solutions fall into a few common patterns:

Local component state
Best for small UI-specific logic.
Props / Inputs and Outputs / Event Emitters
Data flows one way, events travel the other way.
Context / Provide-Inject / Dependency Injection
Used to avoid unnecessary prop drilling.
Global stores using libraries
Redux, Vuex, NgRx, Pinia, Zustand, Jotai, Akita, NGXS.
Signals and fine-grained reactivity
New trend across frameworks.
Server-driven state
React Query, TanStack Query, Apollo Client, Angular Query.

Different frameworks combine these patterns in their own ways. Let’s examine each framework.

3. State Management in React

React has always used a unidirectional data flow model: data flows down from parent to children, and events bubble up. Over time, React added multiple tools for handling state, and this resulted in a large ecosystem of state libraries.

3.1 Local State in React

React components use local state through hooks:

const [count, setCount] = useState(0);

Local state is suitable for UI-level interactions. But once multiple components need access, it becomes difficult to manage.

3.2 Context API

For sharing state globally:

const UserContext = createContext();

Context works well for small applications but does not scale for large global state. Performance issues arise due to unnecessary renders, which led many teams to move towards more specialized state libraries.

3.3 Redux (Traditional Choice)

Redux introduced predictable state, immutability, and a strict architecture.

Pros

Predictable, testable
Large ecosystem
Middleware for async logic

Cons

Verbose
Requires boilerplate
Steep learning curve

3.4 Modern State Libraries in React

To reduce boilerplate and improve performance, new libraries became popular:

Zustand
Jotai
Recoil
MobX
Redux Toolkit (RTK)

Redux Toolkit is essentially the modern way to use Redux with far less boilerplate.

React also has React Query for server state, which focuses on caching, mutation tracking, and revalidation instead of global state.

React is moving towards fine-grained reactivity through Future React (signals-like), but this is still evolving.

4. State Management in Vue

Vue takes a very reactive approach compared to React.

4.1 Local State in Vue

Vue uses ref and reactive:

const count = ref(0);

This gives fine-grained reactivity out of the box. Vue components update automatically when referenced values change.

4.2 Provide / Inject

Vue allows deeper components to receive state without prop drilling:

provide('user', userObject);
inject('user');

4.3 Vuex (Traditional Store)

Vuex has been the main global state solution for years. It has concepts like mutations, actions, getters, and modules.

4.4 Pinia (Modern Vue State Management)

Pinia is the modern recommended store library:

Simpler API
TypeScript-friendly
Works with Composition API
Less boilerplate

Like React Query, Vue also has Vue Query for server-side caching.

5. State Management in Angular

Angular has always been different. It uses:

Dependency Injection
Services
RXJS Observables
Signals (since Angular v16+)
NgRx, NGXS, Akita (popular store libraries)

Angular encourages a very structured approach to state management.

5.1 Local Component State

You can use:

@Component({...})
export class SomeComponent {
  showMenu = false;
}

Or with signals:

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

export class SomeComponent {
  isOpen = signal(false);
}

Angular’s component state is simple and powerful.

5.2 Services as Singletons

Angular services act as global state containers:

@Injectable({ providedIn: 'root' })
export class UserService {
  user$ = new BehaviorSubject<User | null>(null);
}

Services + Observables or services + signals form the basis of global or shared state in Angular.

5.3 RXJS for Async and Data Flow

Angular has embraced RxJS from the beginning. Angular components subscribe to streams and react to changes.

user$ = this.userService.user$;

This works extremely well for handling async operations.

5.4 Global State Libraries in Angular

The most popular enterprise-ready store is NgRx.

Others include:

NGXS
Akita
Signals Store (emerging with Angular's signal-based reactivity)

Why NgRx is popular

Predictable state container
Highly testable
Strong DevTools debugging
Separation of reducer, selectors, actions, effects
Good for enterprise-scale applications with multiple teams

Why NgRx may be too heavy for small apps

NgRx is excellent but requires cognitive overhead. For small or medium apps, services + signals are often enough.

6. Comparing React, Vue, and Angular State Management

Feature	React	Vue	Angular
Reactivity Model	Virtual DOM + hooks	Fine-grained reactivity	Zone.js + signals
Local State	useState, useReducer	ref, reactive	component properties, signals
Global State	Context, Redux, Zustand, Jotai	Provide/Inject, Vuex, Pinia	Services, NgRx, NGXS, Akita
Async State	Fetch, useEffect, Query libraries	Fetch, Vue Query	HttpClient + RxJS
Best for	UI-heavy apps	Data-reactive apps	Enterprise-scale apps

Angular state management stands apart due to its strong architecture using dependency injection and RxJS.

7. Angular-Focused Implementation: Real-World Patterns

Now that we’ve compared frameworks, let's go deep into Angular.

This section provides a step-by-step real-world architecture for managing state using Angular best practices.

We will focus on:

Component state using signals
Shared state using services + signals
Server state using Angular HttpClient and RxJS
Global state using NgRx for enterprise scenarios
Best practices for maintainability
Anti-patterns to avoid

8. Using Signals for Component State

Angular signals are the future of Angular reactivity. They are simpler than RxJS for small local state.

Example

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

@Component({
  selector: 'app-cart-counter',
  template: `
    <div>
      Items: {{ count() }}
      <button (click)="increment()">Add</button>
    </div>
  `
})
export class CartCounterComponent {
  count = signal(0);

  increment() {
    this.count.update(c => c + 1);
  }
}

Signals update the UI immediately and do not require subscriptions or unsubscriptions.

When to use signals

Component-only logic
UI visibility toggles
Simple counters and form states

When not to use signals

Complex async flows
Shared data across multiple components
Server-state caching

For those cases, services or NgRx are better.

9. Shared State Using Services + Signals (Recommended Modern Angular Pattern)

Services act as singletons across the application. By combining services and signals, you get predictable shared state without heavy libraries.

Example: UserStateService

@Injectable({ providedIn: 'root' })
export class UserStateService {
  private user = signal<User | null>(null);
  user$ = computed(() => this.user());

  setUser(user: User) {
    this.user.set(user);
  }

  clearUser() {
    this.user.set(null);
  }
}

Using It in a Component

export class NavbarComponent {
  user = this.userStateService.user$;

  constructor(private userStateService: UserStateService) {}
}

This pattern is clean, testable, and scalable for mid-size applications.

10. Server State in Angular

Server state includes data fetched from APIs: products, user profiles, orders, notifications.

It is fundamentally different from local UI state because:

It needs caching.
It can go stale.
It requires retries and revalidation.
It must reflect server truth, not local assumptions.

Angular uses HttpClient + RxJS

getProducts(): Observable<Product[]> {
  return this.http.get<Product[]>('/api/products');
}

If you want caching or retry logic:

getProducts(): Observable<Product[]> {
  return this.http.get<Product[]>(url).pipe(
    retry(2),
    shareReplay(1)
  );
}

shareReplay(1) caches the last response.

When to use Angular Query (TanStack Query for Angular)

Angular now supports TanStack Query. It automates caching, refetch, invalidation.

Great for

Lists
Infinite scroll
Filters
Real-time updates

11. NgRx for Enterprise State Management

NgRx uses Redux-style unidirectional data flow.

Architecture

Actions describe what happened.
Reducers decide how state changes.
Selectors read state.
Effects handle async logic like HTTP calls.

This pattern is extremely predictable and testable.

Example: Defining Actions

export const loadProducts = createAction('[Products] Load');
export const loadProductsSuccess = createAction(
  '[Products] Load Success',
  props<{ products: Product[] }>()
);

Reducer

export const productsReducer = createReducer(
  initialState,
  on(loadProductsSuccess, (state, { products }) => ({
    ...state,
    products
  }))
);

Selector

export const selectProducts = createSelector(
  selectProductsState,
  (state) => state.products
);

Effect

loadProducts$ = createEffect(() =>this.actions$.pipe(
    ofType(loadProducts),
    mergeMap(() =>
      this.http.get<Product[]>('/api/products').pipe(
        map(products => loadProductsSuccess({ products }))
      )
    )
  )
);

NgRx is ideal when you have:

Multiple teams
Complex domain logic
Shared design system
Multiple modules sharing data
Need for strict debugging and time travel

12. When to Use What in Angular

Use Component State (signals) when:

State is limited to the component
No other component depends on it
No async behavior

Use Services + Signals when:

Multiple components share state
Logic is not too complex
Good for mid-size apps

Use RxJS when

Complex async flows
Cancellation
Combination of multiple streams
Debouncing, throttling

Use NgRx when

Large enterprise
Many modules depend on same state
Predictability is essential
Team size is large

Use Angular Query when

Server state caching is needed
You require background refresh, stale-while-revalidate, optimistic updates

13. Anti-Patterns to Avoid in Angular State Management

Mutating shared state directly.
Using too many BehaviorSubjects instead of signals.
Storing everything in NgRx.
Keeping component logic inside reducers.
Mixing server state with local UI state.
Using async pipes incorrectly, causing multiple HTTP calls.
Overusing local state when global is required.

14. Real-World Example: E-Commerce State Architecture

Let’s design an e-commerce store state structure using recommended Angular practices.

14.1 Local State Examples

Search box input (signal)
Show/hide filter sidebar (signal)

14.2 Shared State Examples

Cart contents (service + signals)
Wishlist (service + signals)

14.3 Server State Examples

Product list (Angular Query)
Product details (Angular Query)
Orders (Angular Query or NgRx depending on complexity)

14.4 Global State (NgRx)

Authentication state
User details
Permissions
Payment configurations
System-wide notifications

This hybrid model is what modern Angular applications use.

15. Patterns for Scaling Large Angular Applications

15.1 Domain-Driven State

Organise state by domain:

user
products
checkout
payments
notifications

Each domain gets:

A service
Optionally a store (NgRx, signals store)
Selectors for reading

15.2 Smart vs Presentational Components

Smart components handle:

Data fetching
Invoking services
Business logic

Presentational components handle:

UI only
Data display
Input/output bindings

15.3 Avoid Tight Coupling

Do not allow UI components to depend directly on NgRx selectors. Use facade services.

Conclusion

State management is one of the most important topics in front-end engineering. React, Vue, and Angular offer different philosophies, but they share common problems:

How to manage local state
How to share state across components
How to manage async server state
How to scale predictable state in large applications

React depends on hooks, contexts, and external state libraries. Vue builds on fine-grained reactivity. Angular uses a structured DI-first approach with signals and RxJS, and optionally NgRx for large-scale apps.

For most modern Angular applications, the best approach is:

Local UI state with signals
Shared state with services + signals
Server async state with Angular Query or RxJS
Global enterprise-level state with NgRx

Choose the right tool for the right layer. This is the secret to building stable, maintainable, and scalable Angular applications.

State Management RxJS Angular Services Angular Signals NgRxReact Stateglobal stateFront End Architecturemodern frontend frameworksVue Pinia

Comments

Join the conversation! Your thoughts help the community grow.