How to keep client-side data always up to date
summary
The talk describes problems encountered during incremental evolution of a service where stale data on client services slowed development, and explains an architectural redesign to ensure client services always have up-to-date data. It details the decisions made to implement the new data delivery system and how Go was used to rapidly build the central component that supplies fresh data to clients.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 4:42Architecture problems
- 5:51Client caching approach
- 8:19Data format and messages
- 10:49Choosing YDB
- 13:18Message processing in Go
- 18:22Using generics for domains
- 21:52Launch and testing
- 25:31Hardware scaling
- 27:16Performance benchmarks
- 29:45Impact on product managers
- 30:47Conclusion and future work
- 31:29Q&A
related talks
44mHow to Keep Client-Side Data Always Fresh
44mHow to Approach Modern Web Applications
15mIncremental Data Architecture
32mCRDT and other new ideas for client-server communication
08mThe End of the Data Ice Age
34mOffline-First Mobile App Design
01h 18mThe future of chat
28mOptimistic updates in a pessimistic world