Rethinking Syncing in iOS
summary
Argues that using eventually‑consistent distributed databases (examples: Couchbase sync server, Realm, Firebase, AWS AppSync) replaces most custom REST sync code by pairing a local mobile DB with a sync server and continuous push‑pull replication. Demo app with Couchbase shows near‑instant updates to the UI when server documents change and simplifies models via codable JSON models. Works well for small, slowly changing master data and offline user‑created content but breaks down on large blobs or a 100–150k records flood and for very fast changing datasets.
AI-written summary · about
chapters (17)
- 0:00Intro
- 3:42Different REST approaches
- 6:41Net Change
- 15:06Complications
- 17:37Database Types
- 18:30Examples
- 18:58Architecture
- 25:13Implementation
- 25:27Model Objects
- 27:05Data Controller
- 32:04Refresh on Change
- 33:03Adding Data
- 33:59Deleting Data
- 34:48Advantages
- 36:21Simplification
- 37:48Disadvantages
- 42:12Best use cases
related talks
18mRethinking Apps with Local-First Architecture
24mGoing Local-First: A Primer
12mWunderlist: High Volume, Multi-Master, Cross-Platform, Distr. DB System
24mEngineering Real-Time Data Synchronization Across Multi-Cloud Systems
21mCRDTs for Mortals
27mFrom Thundering Herd to Zero Outages: Building Reliable Inventory Sync
21mLocal-First in Practice: Learnings of building a high-performance, local-first mus...
28mData corrupting architectures we know and love