Cloud Meets Edge: Embedding Data Processing & Synchronization in Mobile Apps
summary
Inventory demo shows a Kotlin mobile app using a local JSON database (Couchbase Lite) with push/pull replication to a cloud Couchbase cluster via an up-endpoint service; replication runs continuously or on demand, transfers deltas only to save bandwidth, and enforces ACLs by channels so teams see only their warehouses. Offline edits persist and later sync; conflicts resolve by timestamp wins conflict resolution by default. The live demo uses two emulators to prove sync, offline edits, and delayed/conditional replication.
AI-written summary · about
chapters (15)
- 0:00Embedded data processing intro
- 1:04What is Couchbase
- 3:12Traditional cloud architecture
- 5:18Offline app challenges
- 7:27Edge architecture benefits
- 9:59Client-side data processing
- 11:07Client sync complexities
- 13:59Offline-capable architecture
- 16:49Edge devices vs nodes
- 17:10Carnival cruise ship example
- 19:17Warehouse inventory scenario
- 20:45Demo architecture
- 25:01Live inventory sync demo
- 34:19Conflict resolution offline
- 36:07Q&A
related talks
35mSync Data with your Mobile Kotlin App The Easy Way!
45mOffline should be the norm: building local-first apps with CRDTs & Kotlin Multiplatform
47mZero to App Live coding an Android app on Firebase in Kotlin
36mEmbedded NoSQL Data Persistence, Everywhere
47mKotlin on Client and Server
43mFull Stack Kotlin on Google Cloud!
39mBuilding a real-time collaboration tool using CRDTs and Kotlin Multiplatform
23mKotlin Multiplatform Mobile in production: key takeaways from developing two cross-platform apps
