Articles for people who
ship the stack
Original rewrites on React, Node.js, TypeScript and AI — practical notes from the same engineering practice behind our operator software. Article bodies are in English.
Tagged: zustand
Context vs Redux Toolkit vs Zustand for React state
Compare Context, Redux Toolkit, and Zustand for a video portal, then combine client stores with TanStack Query for server state.
7272 wordsRead articleWhy Redux or Zustand Belong With Many Writers, Not Many Readers
Reader count is not enough reason for a client store. Multiple writers sharing invariants — like a shopping cart — are when reducers, replay, and direct tests earn their keep.
2370 wordsRead articleScope State by Lifetime: When a React Portal Actually Needs a Global Store
Learn to decide where React portal state belongs by its owner and lifetime, why global stores create cleanup bugs, and which cases truly justify Redux or Zustand.
768 wordsRead articleMeasuring React State Managers: Render Counts and Bundle Cost Compared
One cart app built with eight React state patterns, measured for wasted renders and gzipped bundle size, and what the numbers say about Zustand, Valtio and Context.
2227 wordsRead articleA Predictable React Baseline with TypeScript, Zustand and Typed Services
A small React, TypeScript and Zustand skeleton that separates stores, typed API services and components, plus conventions for structure, async state and testing.
1207 wordsRead articleZustand vs TanStack Query Boundaries in a Realtime Next.js Monorepo
Learn a clear ownership rule for UI state, server state and realtime events in a collaborative Next.js monorepo using Zustand, TanStack Query and sockets.
2359 wordsRead article
About these articles
Request a 24h estimate
Need the same stack in a production operator layer? Send the brief — estimate within 24 hours.