Skip to content

Latest commit

 

History

History
27 lines (14 loc) · 887 Bytes

Job scheduler.md

File metadata and controls

27 lines (14 loc) · 887 Bytes

Functional requirements:

● Job Editor: The user should be able to add/view/update/delete a job and its schedule

● Job Status: The user should be able to see the status of a job (ready/running/failed/finished)

● Execution History: The user should be able to see the execution history of a job

● Retry Support: The system should be able to retry the failed jobs

● On-time execution: The system should trigger the jobs within 1 minute of the scheduled time

● Recurring jobs: Jobs schedule frequency could be a combination of min/hour/day/week/month

● End date: Recurring jobs may or may not have an end date

Non Functional requirements:

● Low Latency

● High Availability

Full Video Link:

youtube link

IMAGE