storage
Blob storage for system design interviews
Blob storage for system design interviews. Put bytes in an object store, keep the key in a row, and treat the pointer as a separate consistency problem.
All categories
Caching and storage
What you store, where you store it, and how you keep a copy close to the read: caches, CDNs, object stores and specialist databases.
- caching
Caching for system design interviews
Caching for system design interviews. What a cache may get wrong, write policies in one table, and invalidation you can run.
- cdn
CDN for system design interviews
CDN for system design interviews. Edge versus origin, what you may cache, push versus pull, and a hot video or a hot short link.
- search
Elasticsearch for system design interviews
Elasticsearch for system design interviews. The inverted index, relevance versus exact match, and why the search cluster sits beside the source of truth.
- databases
Graph databases for system design interviews
Graph databases for system design interviews. Neighbour walks that explode in SQL, the write cost you take on, and when a recursive query is enough.
- caching
LRU cache for system design interviews
LRU cache for system design interviews. A hash map plus a doubly linked list, constant-time get and put, and the scan that flushes the working set.
- caching
Redis for system design interviews
Redis for system design interviews. Name the structure, name the job, and do not treat persistence as a database you can rebuild from.
- databases
Time series databases for interviews
Time series databases for interviews. Append-heavy writes, range queries, rollups, and why a general store starts to hurt at ingest.