The CTO Podcast with Fexingo · 2026-07-05 · 10 min
This episode dives into the real technical challenge behind Figma's multiplayer architecture: not just cursor sync, but handling over 100,000 simultaneous vector objects in a single file. Lucas and Luna unpack how Figma moved from a naive OT approach to a CRDT-based engine, why they chose WebSocket over WebRTC for state sync, and how they manage undo across hundreds of collaborators without breaking the canvas. They also discuss the hidden cost of 'live' collaboration - battery drain on laptops - and how Figma's team optimized message batching to cut CPU usage by 40%. Plus, a look at the tradeoffs between conflict-free replicated data types and operational transforms for real-time design tools. If you're building any collaborative software, this episode offers a concrete look at the engineering decisions behind a product used by millions. #Figma #CRDT #Multiplayer #RealTimeCollaboration #WebSocket #OperationalTransform #VectorGraphics #CanvasRendering #WebAssembly #BatteryOptimization #MessageBatching #StateSync #UndoHistory #FexingoBusiness #BusinessPodcast #TechnicalLeadership #EngineeringArchitecture #CTOPodcast Keep every episode free: buymeacoffee.com/fexingo
How Airbnb Rebuilt Its Search for 100 Million Listings72 / 100How GitHub Migrated 100 Million Repositories to a New Storage Engine76 / 100How Dropbox Rebuilt Its Sync Engine for 700 Million Users85 / 100How Skyscanner Migrated 300 Microservices to Event-Driven Architecture85 / 100How Palantir Rebuilt Its Foundry Ontology for Government AI Deployments85 / 100