Design a Task Scheduling Service
Last updated: March 12, 2026
Quick Overview
Design a geo-distributed task scheduling system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Elastic
System Design
Product Manager
Elastic
March 12, 2026Product Manager
Technical Screen
System Design
Easy
195
11
2,988 solved
Design a geo-distributed task scheduling system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
System design interviews at Elastic typically last 45-60 minutes. You are expected to drive the conversation, starting from requirements gathering through to a detailed architecture. The interviewer will evaluate your ability to handle ambiguity and make practical engineering decisions.
What the Interviewer Expects
- Clearly define functional and non-functional requirements
- Propose a reasonable high-level architecture with core components
- Choose appropriate data storage solutions with basic justification
- Discuss basic scaling strategies (horizontal scaling, caching)
- Identify potential bottlenecks and suggest simple solutions
Key Topics to Cover
High-level architecture and component design
Monitoring, logging, and alerting
API design and rate limiting
Database selection and data modeling
Message queues and async processing
Load balancing and horizontal scaling
How to Approach This
- Start by clarifying functional and non-functional requirements with the interviewer.
- Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
- Draw a high-level architecture first, then deep dive into 1-2 critical components.
- Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
- Address failure scenarios, monitoring, and how the system handles 10x traffic spikes.
Possible Follow-up Questions
- What monitoring and alerting would you set up on day one?
- How would you handle a 10x increase in traffic overnight?
- How would you handle a region-wide outage?
- How would you handle schema migrations with zero downtime?
Practice a Similar Problem on Codemia
Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.
Solve on CodemiaSample Answer
Requirements
- Functional Requirements:
- Users can create, update, and delete tasks.
- Support scheduling tasks with specific execution times or intervals.
- Provide APIs for querying the status of task...
Capacity Estimation
- Assume our system needs to handle 10 million requests per day.
- This translates to approximately 115 tasks per second (10,000,000 requests / 86,400 seconds).
- If each task execution takes an avera...
Submit Your Answer
Markdown supported