Episode
How Notion Rebuilt Its Block Engine for Hybrid Local-Sync
- Published
- Jun 24, 2026
- Duration seconds
- 366
- 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-block-engine-for-hybrid-local-sync/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-block-engine-for-hybrid-local-sync.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
Notion's block-level architecture was designed for single-user documents. But as the product scaled to 100 million users, real-time collaboration exposed deep cracks in its sync model. This episode unpacks how Notion's engineering team rebuilt its block engine from the ground up — migrating from a naive operational transform approach to a custom hybrid model that blends local-first performance with server-authoritative sync. We walk through the specific tradeoffs they made: why they ditched CRDTs for a timestamped delta approach, how they handled conflict resolution for nested blocks without locking, and the surprising lesson about battery life that shaped their sync cadence. If you're building a collaborative product or thinking about offline-first architecture, this episode has a concrete case you can reference. #Notion #BlockEngine #Collaboration #LocalFirst #SyncArchitecture #OperationalTransform #CRDT #ConflictResolution #OfflineFirst #EngineeringOrg #TechnicalLeadership #CTO #ProductivitySoftware #RealTimeSync #Architecture #FexingoBusiness #BusinessPodcast #BusinessAndTechnology Keep every episode free: buymeacoffee.com/fexingo