Authored pair
Compare.
Durability and media trade-offs vs compute capacity headroom.
All pairs
system · deep · draft
Storage interfaces differ by access model — object (HTTP put/get of blobs), block (volumes as disks), and file (shared filesystems) — with separate durability strategies (replication vs erasure coding) that must stay labeled when illustrative.
Problem. Treating “storage” as one dial hides interface, consistency, and durability trade-offs that dominate latency, cost, and failure domains.
- Scenarios
- 3
- Failures
- 5
- Primary cites
- 10
Open deep page Presenter
system · deep · draft
Compute abstractions range from full guest VMs to containers under cluster managers, event-driven serverless, and batch frameworks — with a hard line between landmark papers (Borg/Omega/K8s lineage) and customer-facing cloud products.
Problem. Collapsing “servers” into one concept hides isolation, packing, scheduling, and scaling semantics that decide cost, blast radius, and operability.
- Scenarios
- 3
- Failures
- 5
- Primary cites
- 12
Open deep page Presenter