Evaluation of Google Docs’ Design
Understand how the collaborative document editing service meets non-functional requirements such as consistency, latency, availability, and scalability through techniques like OT, CRDTs, replication, WebSockets, CDNs, and sharding. Learn how the design maintains reliable conflict resolution, low-latency collaboration, fault tolerance, and horizontal scalability across active documents and distributed components.
We'll cover the following...
Requirements compliance
This lesson will focus on how our design meets the non-functional requirements.
Consistency
We ensure strong consistency for conflict resolution using OTs or CRDTs, with a time-series database preserving the order of operations. Once conflicts are resolved, the final state is persisted, ensuring consistent application of updates.
To keep document state consistent across servers within a data center, updated states are replicated using peer-to-peer ...