System‑design playbook and notes
- GitHub repositories branded as system-design “playbooks” are circulating with condensed interview notes on consistency, caching, queues, and case studies, while Google’s own docs still anchor the collaboration edge cases candidates cite. - Google says up to 100 people can work on a Docs file at once; once 100 or more are accessing it, only the owner and some editors can still edit. - The interview hook is concrete tradeoffs: offline edits, convergence after connection loss, and large-room collaboration limits in a product millions already use. (support.google.com)
Collaborative editing sounds simple on screen: two cursors, one document, no save button. Underneath, the hard part is merging overlapping changes without losing anyone’s work. (research.google.com) Google Research described one approach in a 2009 paper on “Differential Synchronization,” which exchanges deltas instead of whole files and is built to converge even after occasional errors. The paper says the method is fault-tolerant and suited to browser environments. (research.google.com) Google’s current help pages show the user-facing version of those tradeoffs. Up to 100 people with view, edit, or comment permissions can work on a Docs, Sheets, or Slides file at the same time. (support.google.com) When 100 or more people are accessing a file, Google says only the owner and some users with editing permissions can edit it. For larger audiences, Google recommends publishing the file as a web page instead of treating it like a live editing room. (support.google.com) Offline editing adds another constraint. Google says users can keep working in Docs, Sheets, and Slides without an internet connection, but only after enabling offline access in Chrome or Microsoft Edge and saving files locally first. (support.google.com) That is why interview prep material keeps returning to the same questions: what happens after Wi‑Fi drops, which side becomes the source of truth, and how the system reconciles edits when clients reconnect. Those are product questions on the surface and consistency questions underneath. (research.google.com) (support.google.com) The “playbook” side of the story is less a single official release than a wave of public GitHub repositories packaging those ideas for interview prep. One repository, DesignNerds/SystemDesign-Playbook, says it covers 50-plus concepts and problem statements across consistency models, reliability, observability, and real-world case studies. (github.com) Another, ritishBhatoye/maang-system-design-playbook, is organized into sections on fundamentals, tradeoffs, case studies, real-world failures, observability, security, and interview simulation. Its README says it is designed for interview preparation and practical backend thinking. (github.com) That mix explains why Google Docs keeps showing up in system-design discussions. It gives candidates a familiar product, a hard concurrency problem, and a documented limit — 100 simultaneous collaborators — that forces tradeoffs into the open. (support.google.com)
