Evaluation of Google Docs’ Design
Evaluate the Google Docs System Design by assessing how it meets critical non-functional requirements. Analyze strategies for achieving strong consistency using OT and CRDTs, minimizing latency with WebSockets and CDNs, and ensuring high availability and horizontal scalability through microservices and replication.
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 ...