{
  "id": 2140821,
  "title": "Presentation: Why Fetch When You Can Sync? Building Local-First Apps on a Sync Engine Architecture",
  "url": "https://urgent.news/2026/08/20/presentation-why-fetch-when-you-can-sync-building-local-first-apps-on",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-20T13:19:00.000Z",
  "source": {
    "name": "InfoQ",
    "slug": "infoq",
    "url": "https://www.infoq.com/presentations/local-first-sync-engine/"
  },
  "original_language": "en",
  "account": "James Arthur, Co-Founder and CEO of ElectricSQL, delivered a presentation at QCon San Francisco titled \"Why Fetch When You Can Sync? Building Local-First Apps on a Sync Engine Architecture.\" Arthur argued that extending reactivity to the server is the next frontier in frontend architecture. He explained how replacing imperative fetching with declarative data bindings can lead to faster, collaborative, and agentic applications using existing stacks.\n\nArthur referenced Ayrton Senna's quote, stating that if you see a gap and don't pursue it, you're no longer a racing driver. He likened this to developers, who share the need for speed and have evolved web development to build better, faster apps. However, the alpha in client-side reactivity frameworks is now diminishing, and Arthur argued that extending reactivity to the server is where the remaining alpha lies.\n\nBy abstracting away the network and extending reactivity to the server, developers can achieve significant gains in performance and user experience. Arthur demonstrated this model by explaining how local writes can be instantly added as optimistic state to the client store, triggering a re-render and making the user see changes immediately. This local optimistic update is then synchronized with the server in the background. If relevant changes arrive in the database, they are synced back to the client, updating the store and re-rendering the view.\n\nArthur emphasized that clients do not exist in isolation and need to communicate with the server, especially with the increasing server-side activity due to agents. By extending reactivity to the server, developers can eliminate loading spinners and meet the need for speed. This approach also simplifies developer experience by abstracting away manual and imperative data fetching, allowing for declarative data bindings that span the entire stack.\n\nArthur compared this sync-based architecture to React, but for data loading instead of user interface. He noted that React revolutionized client-side development by introducing declarative UE and data bindings. Similarly, his proposed sync architecture abstracts away the network programming, handling concerns like data transfer, placement, retention, and optimizing for various connectivity scenarios, including patchy connectivity or downtime.",
  "summary": "James Arthur shares why sync is the next frontier in frontend architecture. He explains how extending reactivity to the server with Electric and TanStack DB replaces imperative fetching with declarative data bindings. Learn how query-driven sync and local optimistic updates enable engineering leaders to build insanely fast, collaborative, and agentic applications using their existing stack. By…",
  "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."
}