Episode
How Notion Rebuilt Its Sync Engine for Offline-First
- Published
- Jun 24, 2026
- Duration seconds
- 645
- Processing state
not_requested
Actions
POST https://stenobird.com/v1/public/podcasts/the-cto-podcast-with-fexingo-technical-leadership-architecture-and-engineering-org-7871807/episodes/how-notion-rebuilt-its-sync-engine-for-offline-first/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/the-cto-podcast-with-fexingo-technical-leadership-architecture-and-engineering-org-7871807/how-notion-rebuilt-its-sync-engine-for-offline-first.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
Lucas and Luna dive into Notion's technical journey to rebuild its block-based sync engine for offline-first and real-time collaboration. They explore the architectural shift from optimistic local writes to a hybrid local-sync model, the challenges of conflict resolution with operational transforms, and how Notion handled state reconciliation for millions of users. Specific numbers: over 100 million blocks synced daily, sub-second latency for local writes, and a 40% reduction in sync errors post-migration. The episode also touches on the trade-offs between local-first and server-authoritative models, and what other builders can learn from Notion's engineering decisions. #Notion #OfflineFirst #SyncEngine #LocalFirst #OperationalTransform #ConflictResolution #RealTimeCollaboration #BlockEngine #Engineering #Architecture #TechLeadership #CTO #Business #Technology #FexingoBusiness #BusinessPodcast #Scaling #SoftwareEngineering Keep every episode free: buymeacoffee.com/fexingo