Logux — A New Way to Connect Client and Server
summary
Logux is a library and proxy-server approach that replaces AJAX/REST by synchronizing operation logs between client and server. It sends Redux-style actions over WebSocket, supports optimistic UI with local persistence, uses Redis pub/sub and pluggable storage on the server, provides server-side action handlers that can map to existing AJAX endpoints, includes time-delta sync to avoid clock drift, and offers optional CRDT helpers for conflict resolution so it can integrate with legacy backends without a full rewrite.
AI-written summary · about
chapters (32)
- 0:00Introduction
- 1:24Client-server sync problems
- 3:30Logux goals: less offline code
- 5:19Sync via shared DBs
- 7:06Universal DBs failures
- 8:53Sync solutions problems
- 10:42Conflict resolution structure
- 12:30Logux core idea
- 14:14Logux code-level work
- 15:59Action sync offline
- 17:23Time issues solution
- 18:49Replace AJAX REST with Logux
- 20:14Error handling optimistic UI
- 22:40Logux server work
- 24:09Logux server integration
- 25:54Why Logux needed
- 26:54Logux myths vs reality
- 27:59Logux vs Firebase GraphQL Meteor
- 29:02Project state future plans
- 30:03Join development
- 30:46Q&A sync conflicts
- 32:50Q&A vs Meteor others
- 34:15Q&A complex structures
- 35:18Q&A server log storage
- 36:45Q&A log optimization
- 38:10Q&A server replication
- 39:34Q&A project prospects
- 41:00Q&A enterprise proxy
- 42:36Q&A log structure
- 44:51Q&A state optimization
- 46:15Q&A data transfer
- 47:17Q&A non-WebSocket browsers
related talks
34mLogux, a new approach to client-server communication
27mUsing Logux in Production
29m"Optimistic UI with Logux & Ruby"
25mTaming Client-Server Communication
34mPurify your web development with Raxx
45mGetting Pushy: Pushing Data From Server to Browser
43mDesigning Event-driven architectures with AsyncAPI
01h 20mEfficient Client-Server Communication with Differential Synchronization and JSON Patch