estimation
Capacity planning for system design interviews
Capacity planning for system design interviews. QPS, storage, machine count, peak versus average, and the headroom you can defend out loud.
All categories
Observability and ops
Knowing the system is healthy and sizing it before the load arrives: metrics, logs, traces, SLOs and capacity planning.
- architecture
Design job scheduler for the interview
Design job scheduler for the interview. Jobs, schedules, and workers, plus catch-up after a missed window and why exactly-once will not hold.
- observability
Design logging system for the interview
Design logging system for the interview. Agents, a buffer, and a searchable store, plus how logs differ from metrics when a spike arrives.
- observability
Design metrics system for the interview
Design metrics system for the interview. Emit, transport, store, and query time series, then keep cardinality and alerting off the dashboard path.
- scalability
Horizontal scaling for system design interviews
Horizontal scaling for system design interviews. When to add clones behind a balancer, when data refuses to clone, and when a bigger box is enough.
- observability
Observability for system design interviews
Observability for system design interviews. Logs, metrics, and traces as three signals, the question each answers, and cardinality that blows a bill.
- observability
SLO design for system design interviews
SLO design for system design interviews. How an SLI, an SLO, and an SLA differ, and how an error budget changes the week's work.
- observability
Tracing in system design interviews
Tracing in system design interviews. A trace id that follows the request, spans and sampling, what traces miss, and OpenTelemetry as vocabulary.