How to Keep Client-Side Data Always Fresh
summary
The talk covers challenges encountered during the evolutionary development of a service where stale data on client services became a bottleneck, and describes architectural changes made so client services always hold up-to-date data. It explains the design decisions required for that new data-delivery system and how Go was used to quickly implement the central component of the solution.
AI-written summary · about
chapters (9)
- 0:00Welcome
- 1:10Stale data problem
- 5:26Legacy architecture issues
- 10:11New storage choice
- 13:21Handling incoming messages
- 21:50System launch and testing
- 27:31Results and benchmarks
- 30:20Conclusions and recommendations
- 31:23Q&A
related talks
44mHow to keep client-side data always up to date
08mThe End of the Data Ice Age
06mBuilding Server Side API Architecture
27mData Consistency in Microservices Architecture
58mLegacy modernization made practical: A live coding example of modernization patterns
01h 02mTimeless design for cloud-native systems
39mThe Promise of Event Driven Programming with Fast Data
30mThe End of the Data Ice Age