retries
FDE interview questions tagged retries, across every topic.
2 questions · 0 unlocked for you
Concepts behind "retries"
The curriculum that explains the ideas these questions test.
Foundational
Retries, Exponential Backoff and JitterWhen a call fails on a transient error, retrying immediately is the worst thing you can do: it piles load onto an already-struggling service and synchronizes every client into a stampede. Exponential backoff spaces retries out, and jitter de-synchronizes the clients so they stop arriving in lockstep.⚙️ System Design for AI in Production
Core
IdempotencyAn idempotent operation produces the same end state whether you apply it once or five times, which is exactly what you need in a world where retries and at-least-once delivery mean every request may arrive twice. Without it, a single lost response turns one charge into two; with it, the duplicate is a no-op.⚙️ System Design for AI in ProductionSign in
Advanced
Orchestration: DAGs, Retries and BackfillsAn orchestrator runs tasks in dependency order, retries what fails, and lets you re-run history without corrupting it. The scheduling is the easy half. The half that decides whether a deployment survives is whether tasks are idempotent, because an orchestrator's whole value is that it will run things more than once.🗄️ Data & SQL Engineering🔒 Premium