Parece simples até o entrevistador perguntar "why?". Abaixo, uma estrutura de resposta que dá conta do follow-up.
RPS = Requests Per Second — the basic unit for sizing a system.
The math: 1 day = 86,400 seconds. So 1 million requests/day ÷ 86,400 ≈ 12 RPS on average.
Average traffic does not determine the peak. For a practice estimate, explicitly assume a peak multiplier, such as 5x, giving about 58 RPS. In a real design, use measured arrival patterns.
Capacity also depends on work per request. Under steady-state conditions, average in-flight work is approximately arrival rate times average time in the system. At 60 RPS and 2 seconds per request, expect about 120 requests in flight. State the latency, payload, and dependency assumptions before choosing infrastructure.
Ler é o primeiro passo. No app, essa pergunta vira flashcard com repetição espaçada, e o módulo tem quiz e simulado para testar o que ficou.
Treinar essa pergunta no app