Course contentsShow
← React
Lesson 1719 of 2,39641. State Management EcosystemFree lesson

Jotai's Atomic State Philosophy

How Jotai treats each piece of state as an independent atom, avoiding the single-store paradigm.

What You'll Learn

You'll understand how Jotai's atomic approach to state management differs fundamentally from the single-store paradigm used by Redux and Zustand.

The Single-Store Problem

Up until now, you've seen state management solutions that use one central store (Redux, Zustand). You define all your state in one place, then components subscribe to slices of that store. This works, but it creates coupling—every piece of state lives in the same bucket, even if they're completely unrelated.

Jotai's Atomic Philosophy

Jotai flips this model on its head. Instead of one big store, each piece of state is an independent "atom"—a tiny, self-contained unit that lives on its own. Think of atoms like individual variables floating in space, rather than properties in a massive object.

An atom is both:

  • A definition of a piece of state (like declaring a variable)
  • A subscription point that components can read from and write to

There's no provider wrapping your app (like Context), and no single store object (like Zustand). Atoms exist globally but are consumed locally—only the components that use a specific atom re-render when that atom changes.

The Mental Model Shift

Instead of thinking "I need to add this to my store," you think "I need to create a new atom for this piece of state." Each atom is isolated by default. You can still compose them together (atoms can depend on other atoms), but the default is independence, not centralization.

This makes Jotai feel more like React's useState, but with global reach. Each atom behaves like a separate state variable, accessible anywhere.

Key Takeaway: Jotai treats state as independent atoms, not as slices of a single store—maximizing isolation and minimizing coupling between unrelated state.