Patterns
Read-heavy Systems
A read-heavy system has far more reads than writes. In interviews, the main goal is to make the read path fast, cheap, and reliable. What it means A system is read-heavy when users read data much more often than they create or update it. Examples: * URL shortener redirects