Design Task Scheduling Infrastructure for real-time analytics

Last updated: July 25, 2025

Quick Overview

Design a distributed task scheduling system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

Amazon
System Design
Software Engineer
Amazon
July 25, 2025
Software Engineer
Onsite
System Design
Easy

147

9

2,092 solved


Design a distributed task scheduling system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

System design interviews at Amazon 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
Consistency models and replication
Requirements gathering and capacity estimation
Monitoring, logging, and alerting
High-level architecture and component design
How to Approach This
  1. Start by clarifying functional and non-functional requirements with the interviewer.
  2. Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
  3. Draw a high-level architecture first, then deep dive into 1-2 critical components.
  4. Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
  5. Address failure scenarios, monitoring, and how the system handles 10x traffic spikes.
Possible Follow-up Questions
  • How would you optimize costs as the system scales?
  • How would you handle schema migrations with zero downtime?
  • How would you handle a region-wide outage?
Practice a Similar Problem on Codemia

Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.

Solve on Codemia
Sample Answer
Requirements

Functional Requirements

  1. Task Creation: Users must be able to submit tasks with specific parameters, including task type, priority, and execution time.
  2. Task Scheduling: The system mus...
Capacity Estimation

Assuming we are handling 1 million tasks per minute:

  • Total Tasks Per Second: 1,000,000 / 60 ≈ 16,667 tasks/second.
  • Task Execution Time: Assuming an average task execution time of 100ms, ea...

Submit Your Answer
Markdown supported

Related Questions