nutcas3/phone-system-design-framework

This repository is a study guide and reference framework for software engineering interviews focused on system design. The core idea is that a smartphone is essentially a distributed computing system packed into a single device, facing the same engineering challenges as large-scale cloud platforms: latency constraints, resource limits, parallel processing, fault tolerance, and security isolation. By understanding how a phone is built, an engineer can reason about how to design any large distributed system. The document is structured as a series of mappings between smartphone hardware components and their equivalents in cloud infrastructure. The first section covers CPU architecture: modern phone chips use two classes of processing cores, high-power ones for demanding tasks like video rendering or AI and low-power ones for background tasks like syncing email. The guide maps this to backend compute clusters, where some server pools handle heavy batch work (video transcoding, search indexing) and others handle lightweight, high-frequency user requests (logins, comments). The key principle is that different workloads should not compete for the same resources. The second section covers memory hierarchy. A phone cannot read from its flash storage directly for active work because storage is tens of thousands of times slower than memory. So data is kept at the right level: the fastest caches hold the most frequently accessed data, and slower storage holds the rest. The guide maps each layer (CPU caches, RAM, flash storage, external cards) to a corresponding tier in distributed systems (in-process caches, local caches, Redis, databases, and cold object storage like S3). The principle is the same: serve data from the fastest layer that has it. Further sections visible in the README cover communication between components, mapping smartphone inter-process communication (the structured channels through which apps exchange data) to API gateways, service meshes, and message queues. Each section includes sample interview question exchanges showing how to use the phone analogy to structure an answer about designing a real system like YouTube or a trading platform. The framework is intended as a mental model, not a checklist.