Koder Cron — Distributed Job Scheduler

• *rea:*Data Platform
• *ath:*data/cron
• *ind:*Go service + CLI — job scheduling and workflow orchestration

Role in the stack

Distributed job scheduler and workflow engine. Any Koder service that needs to run background tasks on a schedule (cron syntax), with delay, with retries, or as a DAG of dependent steps, uses Cron as its execution substrate. Replaces ad-hoc goroutine timers and crontab entries across the fleet.

Features

• Standard 5field and extended 6field (with seconds) cron expressions, timezone support
• One-time delayed jobs and recurring jobs
• DAG execution — jobs can declare dependencies; Cron resolves order and runs in parallel where possible
• Retry with exponential backoff, dead-letter queue
• Distributed locking — only one instance picks up each job across a cluster
• HTTP + gRPC APIs for job registration, status, history
• CLI (koder-cron) for operator use

Primary couplings

Interfaces

• gRPC API — JobService (schedule, cancel, status, list)
• HTTP REST API — POST /jobs, GET /jobs/{id}, DELETE /jobs/{id}
• CLI — koder-cron schedule, koder-cron list, koder-cron run

Status

Active — deployed for internal use. Landing page at infra/data/cron/site/.