Ƙera offline sync don manhajar koyo: yaya kake warware conflicts?

Question

IT Interview Practice · Accepted Answer

Ka ɗauki manhajar a matsayin **offline-first**: kowace na'ura wata **replica** ce ta cikin gida. Ana rubuta ayyukan karatu zuwa **local DB** tare da **op log** mai ƙari-kawai (outbox); idan aka sake haɗawa, na'urar tana **turawa da ops ɗinta** kuma tana **jawo canje-canjen server** tun sync ɗin ƙarshe. Ba a warware conflicts **da doka guda ɗaya ta gaba ɗaya ba** sai dai da **semantics na kowane data field**.

**Tunanin fahimta:** ka yi tunaninsa kamar **git** — kowace na'ura tana yin "commit" a cikin gida yayin da take offline, kuma sync **merge** ne, ba rubutu a kai ba.

## Gine-gine

```text
Device (offline)                        Server = source of truth
┌──────────────────┐   on reconnect     ┌───────────────────────────┐
│ Local DB (SQLite)│  push ops (delta)  │ Sync API  /sync           │
│ + Op log (outbox)│ ─────────────────▶ │  • idempotent by op.id    │
│ cursor = lastSeen│ ◀───────────────── │  • merge by semantics     │
└──────────────────┘  pull changes>cursor└───────────────────────────┘
                                         Progress DB (Postgres)
```

- **Local DB + op log:** kowane canji **immutable op ne mai id da client ya ƙirƙira** + version, ana jera shi yayin offline. UI tana karantawa/rubutawa a cikin gida don haka tana ci gaba da santsi ba tare da network ba.
- **Sync service:** **cursor-based delta** sync — tura ops tun cursor ɗin client, jawo canje-canjen da suka fi shi sabo. Kowane sync yana motsa **delta** kawai, ba dukan dataset ba → masu amfani miliyan 5 na ci gaba da zama masu arha.
- **Conflict resolver:** yana merge bisa ma'anar kowane field (a ƙasa). **Server shi ne source of truth**; client yana warwarewa da farko don santsi, sannan server yana sake amfani da **merge deterministic iri ɗaya**.

## Warware conflict (ainihin abin)

Agogon waya **ba abin dogaro ba ne** kuma na'urori biyu za su iya gyara record iri ɗaya offline, don haka **"last write wins" (LWW) yana asarar data a shiru**. Warware da semantics:

- **Monotonic fields** (ci gaban darasi) → ɗauki **max**.
- **Additive counters** (jimlar lokacin karatu) → **ƙara delta** (CRDT-style grow-only counter).
- **"Latest state" na gaskiya** (scroll position) → LWW yana karɓuwa.

```js
// op yana da id -> aiwatar da idempotently (retries ba sa ƙidaya sau biyu). clientTs BA a amincewa da shi ba.
function mergeProgress(server, op) {
  return {
    // progress kawai yana ƙaruwa -> max: tsohon op da ya makara ba zai taɓa jan shi baya ba
    progress: Math.max(server.progress ?? 0, op.progress),
    // studiedMs additive counter ne -> ƙara delta, kada ka rubuta a kai
    studiedMs: (server.studiedMs ?? 0) + op.studiedMs,
    completedAt: server.completedAt ?? (op.progress >= 1 ? op.clientTs : null),
  };
}
```

A nan, LWW mara-tsari zai bar na'urar tsohuwa da ke yin sync a makare da `progress: 0.3` ta **rubuta a kan** `0.9` na server → asarar ci gaba. Ɗaukar `max` da haɗa `studiedMs` yana sa sync **order-independent** — mai aminci lokacin da na'urori miliyoyi ke yin sync da agogo marasa daidaito.

## Mahangar hira

Mai hirar yana bincike ko ka san **ba za a amince da agogon client ba** (don haka ba timestamp LWW kaɗai ba), ko kana sa **sync ya zama idempotent** (op ids), da kuma ko kana **merge bisa ma'anar data**. Amsa **mai rauni**: "yi amfani da timestamps, last write wins." Amsa **mai ƙarfi**: replica + op log + idempotency + per-field merge + server a matsayin source of truth — tare da ambaton gazawar **asarar data** ta LWW a fili.

## Fa'ida da hasara

LWW yana da arha amma yana asara; semantic merge yana buƙatar tunani a kowane field amma **ba ya rasa komai**. Ka nemi cikakken **CRDT/OT** kawai lokacin da kake buƙatar gyara na haɗin gwiwa na gaskiya (notes, documents) — yana da tsada, don haka kada ka yi amfani da shi ga komai.

Gine-gine

Warware conflict (ainihin abin)

Mahangar hira

Fa'ida da hasara

Tambayoyi masu alaƙa