Requirements

Functional Requirements:

• User should be able to schedule a task
• A scheduled task should be executed at the schedule
• When a task is executed a user should be made aware

Non-Functional Requirements:

• The system should be able to handle millions of concurrent schedules and task executions
• If a task fails to schedule or during execution the system should be able to retry a certain number of times and to habdle failures

API Design

Define the APIs expected from the system. This is your chance to analyze and define the read and write paths so that you can come up with the high-level design...

• POST /task endpoint to submit task schedules
• GET /task/id endpoint to view the update of a particula

High-Level Design

Describe the overall system architecture. Identify the main components needed to solve the problem end-to-end. Use the diagramming tool to create a block diagram.

Detailed Component Design

Deep dive into 2-3 key components. Explain how they work, how they scale, discuss tradeoffs, capacity, and any relevant algorithms or data structures.

• The tasks can be stored as objects in dynamodb since theres not gonna be any relation and ACID compliance is not required