Offline-first data: Getting Bigger

on YouTube ↗25m

" summary

An offline‑first web system actually ships service workers, PouchDB & CouchDB and a remote ID dispenser to assign per‑user partitions so only the needed subset of data syncs; it runs against 30,000 clinics and scales by switching network storage adapters between local and remote on demand. Concrete surprises: time‑windowed data breaks balances, JSON normalization vs denormalization forces bulk updates, and serverless lambdas can DDoS the central DB if not throttled.

AI-written summary · about

" chapters (13)

1. 0:00Intro
2. 0:33Patricia Garcia
3. 1:19What tech stack do you use
4. 3:36Abuja and Lagos
5. 4:49Offline Capability
6. 8:53Replication
7. 9:20Problems
8. 10:21Bigger scale
9. 10:51Syncing data
10. 12:56Network storage
11. 13:54JSON modeling
12. 17:57Network storage adapters
13. 19:04User experience

" related talks

• 49mOfflineFirst Apps with PouchDB and CouchDBLorna Jane Mitchell · Front End North 2018
• 51mFront End DataJing Chen, Jake Archibald, Nolan Lawson, Matt MacPherson, David Fahlander, Glynn Bird · Edge Conference 2015
• 51mCouchDB, PouchDB and Offline-Tolerant AppsLorna Jane Mitchell · Dutch PHP Conference 2017
• 47mThe future of Real-time/offline/dataNader Dabit · Agent Conf 2020
• 41mSync is the Future of Mobile DataChris Anderson · Strange Loop 2013
• 32mLow Latency Serving of Offline Data: Efficient, Safe, and Reliable Data...William Schor · SREcon26 Americas
• 45mThe Future of Data in EmberDan Gebhardt · EmberConf 2018
• 33mData.jsMichael Aufreiter · JSConf EU 2011