Kuna nini kuwa na kawaida ya hali?

Question

Accepted Answer

**Kuwa na kawaida** kumaanisha kuhifadhi data katika muundo wa gorofa, wa uhusiano — iliyotengenezwa kwa **id** katika jedwali za tafuta — badala ya vitu/mkumbo vilivyofungwa kwa kina. Ni wazo sawa na kuwa na kawaida ya hifadhi ya data, inayotumika katika hali ya mteja, na inafanya sasisho na utafutaji kuwa wa haraka na thabiti.

## Tatizo la hali iliyofungwa/isiyo na kawaida

```js
// ❌ nested & duplicated — the same user appears in multiple posts
posts: [
  { id: 1, title: "A", author: { id: 10, name: "Ann" } },
  { id: 2, title: "B", author: { id: 10, name: "Ann" } }, // Ann duplicated
]
// To rename Ann, you must find and update EVERY copy → easy to miss one (drift)
// To find post #2, you must scan the array
```

Data iliyofungwa inayorudiwa lazima isasishwe katika maeneo mengi (hatari ya kutokuwa na thabiti), na kupata kitu kumaanisha kuchanganua mkumbo (O(n)).

## Muundo unaojulikana kwa kawaida

```js
// ✅ flat lookup tables keyed by id, with references by id
{
  posts: {
    byId: { 1: { id: 1, title: "A", authorId: 10 },   // reference the author by id
            2: { id: 2, title: "B", authorId: 10 } },
    allIds: [1, 2],                                     // order/iteration
  },
  users: {
    byId: { 10: { id: 10, name: "Ann" } },             // each user stored ONCE
  },
}
```

Kila huluki huhifadhiwa mara moja, iliyotengenezwa kwa id; uhusiano ni rafiki za id tu.

## Faida

```js
state.users.byId[10];                        // ✅ O(1) lookup by id
state.users.byId[10] = { ...u, name: "Bob" }; // ✅ update Ann ONCE → reflected everywhere
state.posts.allIds.map(id => state.posts.byId[id]); // iterate via the id list
```

```text
✓ Single source of truth per entity → no duplication, no drift
✓ O(1) lookups/updates by id (vs scanning arrays)
✓ Easy to update one entity and have all references reflect it
✓ Simpler to manage relationships and merge new data
```

## Zana

```text
Redux Toolkit's createEntityAdapter generates normalized { ids, entities }
structures + CRUD reducers automatically. normalizr can normalize API responses.
```

## Kwa nini ni muhimu

Kuwa na kawaida ni muundo wa kawaida wa kusimamia **data ya uhusiano/mkusanyo** katika hali ya mteja (hasa katika Redux).

Inafanya ili kuwe na chanzo kimoja cha ukweli kwa huluki (sasisho mara moja, kutapatapa kila mahali), inatoa utafutaji wa haraka wa kulingana na id, na kuepuka matatizo na matatizo ya utendaji wa data iliyofungwa kwa kina na inayorudiwa.

Kwa programu na orodha za huluki zinazohusiana (watumiaji, chapisho, maoni) zinazosasishwa na kureferenziwa sambamba, kuwa na kawaida kwa duka — mara nyingi kupitia `createEntityAdapter` — ni ujinga muhimu wa kuweka hali kuwa na thabiti na wa haraka.