Hard Design: Distributed Task Scheduler (Cron at Scale)
Why is a single-server cron scheduler not suitable for production at scale?
— Tests your understanding of this concept.
Answer Options
A Cron expressions are too complex
B Single server is a single point of failure — if it crashes, no jobs run
C Cron cannot handle more than 1000 jobs
D Cron doesn't support retry logic
Want to see the correct answer?
Get the answer with a detailed explanation, plus practice 22+ more Design: Distributed Task Scheduler (Cron at Scale) questions with adaptive quizzes and timed interviews.
See the Answer on Guru Sishya →This question is from the Design: Distributed Task Scheduler (Cron at Scale) topic (System Design Cases).
More Design: Distributed Task Scheduler (Cron at Scale) Questions
What is the purpose of leader election in a distributed task scheduler?
HardA worker picks up a task and starts executing. The worker crashes mid-execution. What happens?
HardWhat is the 'thundering herd' problem in a task scheduler?
HardHow do you calculate the next_run_at for a cron expression after a successful execution?
HardWhat Redis command is used to implement a distributed lock for exactly-once task execution?
Hard