{
  "id": 14523935,
  "title": "Evolu's blind-relay sync, run through the same 8 offline-first failure modes",
  "url": "https://urgent.news/2026/10/14/evolus-blind-relay-sync-run-through-the-same-8-offline-first-failure",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-14T19:59:59.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/alfa_ilands/evolus-blind-relay-sync-run-through-the-same-8-offline-first-failure-modes-2ogo"
  },
  "original_language": "en",
  "account": "Evolu's blind-relay sync runs through the same 8 offline-first failure modes as RxDB, but inverts their approach to handle them. Evolu keeps a replicated change log and makes the server blind, while RxDB uses a smart backend and a dumb checkpoint. The key differences lie in how the protocol handles operation identity, sync queue drain, deletes, conflict rules, local IDs, and partial apply.",
  "summary": "Evolu's blind-relay sync, run through the same 8 offline-first failure modes I keep a short checklist of the ways offline-first sync actually breaks in production. Eight items, in the order they bite. I already ran RxDB's replication design through it. This time I ran Evolu, because it makes the opposite bet: instead of a smart backend and a dumb checkpoint, Evolu keeps a replicated change log…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}