How to Approach Modern Web Applications
summary
Presents a concrete architecture for modern web apps: normalize data into a separate client-side model run in an in-memory database, record user actions in an event log and sync those logs with the server, and use optimistic rendering/optimistic UI while background sync and server pushes arrive. Demonstrates a Cognition-based web platform with interactive widgets, discusses inevitable conflict resolution, and compares server rendering versus sync tradeoffs to explain practical implementation choices.
AI-written summary · about
chapters (19)
- 0:00Modern web apps intro
- 1:59App architecture approach
- 5:08Basic web app limits
- 6:11Model data first
- 7:53Nested data issues
- 9:38Normalize for flexibility
- 10:20In-memory database use
- 13:55Server sync problems
- 17:27Centralized sync needed
- 18:50Event log for sync
- 20:36Why event log helps sync
- 22:20Optimistic UI and lag
- 23:45Reactivity and collaboration
- 24:49Distributed conflicts
- 26:59Conflict resolution context
- 29:11Final app architecture
- 30:12SSR role
- 32:18Summary
- 33:24Q&A
related talks
54mHow to build the modern, optimistic and reactive user interface, we all want.
01h 24mWebinar: Architecture of a modern web app
41mModel-View-Websockets
01h 00mFrom Mosaic to Modern: The Evolution of Web App Architectures
47mCreating the Web Applications of the Future, Today
18mThe need for speed - Single-page apps, Optimistic UIs, Reactivity
10mUniversal Apps: Architecture for the Modern Web
36mKnowing What You See - Let's Talk About Front-end Consistency