Kepiye cara sampeyan mutusake ing ngendi saben piece of state kudu manggon?

Question

Accepted Answer

Mutusake **ngendi state manggon** minangka salah siji saka keahlian arsitektur sing paling penting. Prinsip panuntun: sijine saben piece of state ing **scope sing paling sempit** sing isih bisa nyukupi sapa wae sing perlu - lan cocokake saben *jenis* state karo tool sing bener.

## Framework keputusan

```text
1. Who needs this state?
   - One component                  → local state (useState)
   - A few related components        → lift to common parent / small context
   - Many distant components         → global store or context

2. What KIND of state is it?
   - Server/remote data              → server-state library (React Query/SWR)
   - UI/client state                 → useState / Zustand / Redux
   - URL-derivable (filters, page)    → the URL (searchParams)
   - Form input                       → form library or local state

3. How OFTEN does it change?
   - Rarely, widely shared (theme)    → Context is fine
   - Frequently, widely shared        → store with selective subscriptions
```

## Kategori lan tempat-tempate

```text
State type     Lives in                       Examples
─────────────────────────────────────────────────────────────────
Local UI       component (useState)           input text, isOpen, hover
Shared UI      lifted parent / Context / store modal state, selected item
Server data    React Query / SWR / RTK Query  users, products (cached remote)
URL state      router / searchParams          filters, page, search query, tab
Form state     React Hook Form / local         field values, validation
Global app     Zustand / Redux / Context      auth user, theme, cart
```

## Kesalahan umum sing framework cegah

```text
❌ Server data in Redux       → use React Query (it's a cache, not UI state)
❌ Everything global "just in case" → over-coupling, extra re-renders; keep local
❌ Filters/page in state       → put in the URL (shareable, bookmarkable, back-button)
❌ Duplicating derivable values → derive instead (single source of truth)
❌ Form state in a global store → usually overkill; keep local or use a form lib
```

## URL minangka state sing ora digunakake kanthi maksimal

```text
Filters, pagination, search, active tab → belong in the URL.
Benefits: shareable links, browser back/forward works, survives refresh, SEO.
```

## Ngapa penting

Ngendi state manggon nemtokake kesederhanaan, performance, lan maintainability aplikasi.

Kekeahlian yaiku mungkir dorongan kanggo nggawe kabeh global lan malah **nglokalisasi secara default, cocokake saben jenis state karo tool sing tepat** (server data → React Query, bisa diturunake saka URL → URL, UI → lokal/store).

Gawe iki kanthi bener ngilangi masalah arsitektur paling umum - server data dijejalake ing Redux, state sing terlalu global nyebabake re-render, lan filter ing component state tinimbang URL.

Keputusan iki sing mbedakake arsitektur state sing resik lan scalable saka sing kusut.