Performance measures how efficiently and responsively a software system serves specified workloads and operating conditions. In system design, caching improves performance by reducing latency, backend pressure, and repeated computation. section 6.4
Evaluate performance by examining where data is served and which trade-offs each layer introduces:
- Client-side caching can provide instant access without a network request, but requires careful versioning to avoid outdated content. section 6.4
- CDN caching serves content from geographically distributed edge servers, reducing latency and origin-server work while requiring expiration and purging rules. section 6.4
- Application-level caching stores frequently accessed or computed data in memory, speeding responses and reducing database load while complicating distributed consistency. section 6.4
Interview example: an LRU cache
A TypeScript LRU cache keeps recently accessed entries and removes the least recently used key when capacity is exceeded. Discussing its get and put operations demonstrates how an implementation choice affects memory usage and response speed.






















































