How Notion Rebuilt Its Block Engine for Hybrid Local-Sync

Episode notes

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

• How Airbnb Rebuilt Search for 8 Million Listings62 / 100
• How GitLab Built a Single Codebase for One Million CI Pipelines65 / 100
• How Slack Rebuilt Its Search Index for 10 Million Daily Queries57 / 100
• How Notion Rebuilt Its Sync Engine for Offline-First
• How MongoDB Rebuilt Its Document Store for Multi-Terabyte Workloads