Design log search for four hundred services and fifty teams, at ten terabytes a day.

The hard parts are not search. They are deciding what to keep before you pay to store it, isolating one team's query from everyone else's, and making the cost visible to the people generating it.

Updated Sep 2026 · Grounded in researched DevOps, SRE and platform engineering interview loops, written to a senior-engineer editorial bar, and never padded to hit a word count.

The hard parts are not search. They are deciding what to keep before you pay to store it, isolating one team's query from everyone else's, and making the cost visible to the people generating it.

20 answers per topic instead of 10, and your progress kept · no cardor unlock all 390 remaining answers · ₹2,000 / $25

UP NEXT ON YOUR JOURNEY

Next in this trackForty teams want to call models. Design the gateway that sits between them and the providers.Popular right nowWhat happens at the kernel level on SIGTERM versus SIGKILL, and why might a container ignore SIGTERM?Popular right nowAt what layer should this load balancer operate? Explain the trade-off between L4 and L7.

DISCUSSION · 0

Nothing here yet. Say how you would answer it.