State management
State management is the practice of organizing, maintaining, and updating information that represents a system’s or process’s condition over time.
Build a Frontend Web Framework (From Scratch)
A state manager is a software mechanism that stores application state, processes state changes, and coordinates updates to dependent views.
- How it is used
- Keeps application state and the rendered view synchronized as user interactions produce commands.
- How deep it goes
- Builds dispatcher subscriptions, reducer updates, and re-rendering; defers selective DOM updates and skips checking whether every command changed state.
- Examples
- Uses TODO interactions and a removeTodo reducer, with a counter exercise for choosing commands.
- What you can do after
- Build it from scratch by wiring command-specific reducers to stored state and an after-command renderer.
Read how Build a Frontend Web Framework (From Scratch) explains state management →
Build AI-Enhanced Web Apps
State management is the organization, storage, and updating of application state over time.
- How it is used
- Organizes chat interaction, conversation context, and shared AI/UI data across client and server.
- How deep it goes
- Works through hook-level updates, provider setup, synchronization, persistence choices, and debugging guidance rather than only defining the term.
- Examples
- Uses a message-rendering chat list, a submission hook, a profile-and-settings provider, and Redis-backed interview sessions.
- What you can do after
- Build it from scratch with a React hook, or apply it via the Vercel AI SDK’s createAI provider.
Read how Build AI-Enhanced Web Apps explains state management →
Modern Angular
State management is the practice of storing, updating, and sharing application state across software components.
- How it is used
- Centralizes shared feature data and behavior so multiple Angular components can consume reactive state.
- How deep it goes
- Works through a signal-and-RxJS service implementation, including derived request state, event streams, and component delegation.
- Examples
- Uses authentication status and an HR time-off workflow with filtering, approval, rejection, deletion, and a TimeOffManagementComponent.
- What you can do after
- Build it from scratch as a lightweight signal-based service that handles event streams and exposes shared reactive state.
Building Reliable AI Systems
State management is the handling and maintenance of an application's current state as it executes and responds to interactions.
- How it is used
- Preserves specialized agents’ work across a routed workflow so synthesis can produce one response to a multipart request.
- How deep it goes
- Defines shared state and its place among graph nodes and edges, but does not specify a state schema in the supplied excerpts.
- Examples
- Uses a boot-photo request combining image analysis, product search, and return-policy retrieval to illustrate information that must survive coordination.
- What you can do after
- Apply it via LangGraph to share agent results across a workflow and test whether context survives blended requests and failures.
Read how Building Reliable AI Systems explains state management →
Software Testing with Generative AI
State management is the control and maintenance of the system conditions required for an operation or test.
- How it is used
- Uses APIs, databases, test-data managers, or infrastructure tools to establish test conditions at an appropriate layer.
- How deep it goes
- Demonstrates request capture, prompt constraints, POJO modeling, and API setup, but omits HTTP-response parsing.
- Examples
- Uses a Contact Us message, a captured curl command, a Java MessagePayload, and an Admin-panel visibility check.
- What you can do after
- Apply it via API calls and Spring-based Java helpers to make UI checks faster and less brittle.
Read how Software Testing with Generative AI explains state management →
Build Python Web Apps with Streamlit
State management is the practice of retaining and updating application data that determines behavior across interactions or executions.
- How it is used
- Uses state management to preserve a quiz game's progress across Streamlit reruns.
- How deep it goes
- Defines a stateful Game object, session storage, current values, and status-driven branches; defers persistent storage.
- Examples
- Demonstrates Fact Frenzy through question retrieval, answer submission, evaluation, and result display.
- What you can do after
- Apply it via Streamlit to preserve a Game instance and move a quiz through sequential states.
Read how Build Python Web Apps with Streamlit explains state management →
React in Depth
The organization, updating, and synchronization of data representing an application's current state.
- How it is used
- Frames state management as a React ecosystem concern used to select libraries appropriate to project needs.
- How deep it goes
- Compares library choices across project scenarios but stops short of implementation mechanics and state-update internals.
- Examples
- Uses RTK, Zustand, and Redux in e-commerce, portfolio, and legacy enterprise-dashboard stack scenarios.
- What you can do after
- Evaluate state-management libraries and choose a project-fit stack for complex React applications.
AI Agents and Applications
State management is the controlled maintenance and updating of information representing a workflow's current condition across its processing steps.
- How it is used
- Coordinates data across multi-step LangGraph workflows that branch, repeat, preserve context, and support debugging.
- How deep it goes
- Defines TypedDict state, node updates, graph routing, and accumulated execution history, without detailing storage or persistence internals.
- Examples
- Uses a typed research assistant whose search loop evaluates summary relevance before refining queries or writing a final report.
- What you can do after
- Build it from scratch with TypedDict, StateGraph, node functions, directed edges, and conditional routing.
Read how AI Agents and Applications explains state management →
Architecting an Apache Iceberg Lakehouse
State management is the persistence, tracking, and restoration of intermediate processing state in a long-running data workflow.
- How it is used
- Supports reliable recovery and context-aware processing in long-running streaming ingestion pipelines.
- How deep it goes
- Explains persistence, checkpoint-based recovery, transactional completion, and commit tradeoffs without detailing checkpoint implementation.
- Examples
- Uses deduplication, sessionization, and change data capture as stateful transformation examples.
- What you can do after
- Operate streaming recovery with Apache Flink checkpointing and transactional table commits.
Read how Architecting an Apache Iceberg Lakehouse explains state management →
Related concepts
- LangGraphused by · LangGraph is a framework for building stateful, graph-structured workflows and applications, including those involving language models and agents.
- state persistenceuses · State persistence is the retention of data or application state beyond the operation, session, or process in which it was created, so it remains available for later use.
- source of truthconfigures · A source of truth is the authoritative source or representation from which the accepted value or state of information is determined.
- reduction operationuses · A reduction operation combines multiple input values or partial results according to a combining rule to produce fewer results, often a single aggregate.
- rendereruses · A renderer is software that transforms a formal or interface representation into output for display.
- sessionuses · A session is a bounded interaction context associated with a user, client, or process that may maintain state across related operations or requests.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.