Using Logux in Production
summary
Logux claims to replace AJAX/REST with a single append‑only action log that synchronizes via WebSockets, gives optimistic UI with server undo, and transparently handles offline and cross‑tab sync using leader election across tabs. The client is tiny — 12 kilobytes client — and server callbacks let any database stay in place; snapshots every ~100 actions prevent unbounded history. The system is used in production, survives flaky networks (tested in China) and handles concurrent edits by ordering actions deterministically.
AI-written summary · about
chapters (4)
- 0:00Start
- 9:58Conflict Free Replica Data Types
- 24:47Custom Api Error Handling
- 25:32How Does Websocket a Form under Poor Network Connection
related talks
34mLogux, a new approach to client-server communication
48mLogux — A New Way to Connect Client and Server
29m"Optimistic UI with Logux & Ruby"
41mThe UI/UX Benefits and Trade-Offs of Local-First Apps
18mLeading edge: Sync solutions for connecting offline-apps
32mCRDT and other new ideas for client-server communication
47mThe future of Real-time/offline/data
18mThe need for speed - Single-page apps, Optimistic UIs, Reactivity