dkron-io/dkron

Features

• Distributed Job Schedulers - Executes commands across a cluster on a defined schedule to ensure tasks run reliably even if individual servers experience unexpected failures.
• Distributed Recurring Task Scheduling - A fault-tolerant system for scheduling and executing recurring tasks across a cluster of nodes using a consensus protocol.
• Consensus Engines - Elects a leader node using a consensus protocol to manage scheduling and prevent duplicate job executions across multiple servers.
• Distributed Task Orchestration - Distributes scheduled workloads across a cluster of nodes by matching job requirements against available infrastructure tags and capacity.
• Distributed Workflow Orchestrators - Manages complex job dependencies and execution results across multiple servers using a centralized scheduling and monitoring engine.
• Cron Orchestrators - A platform for managing complex workflows and cron-based job dependencies across distributed infrastructure with automatic retries and timeouts.
• Recurring Job Scheduling - Runs tasks on a cron-based timetable using extended syntax and job dependencies to manage complex workflows across a distributed cluster.
• Raft Consensus Implementations - Uses a distributed consensus algorithm to elect a leader node that coordinates job scheduling and maintains cluster state consistency.
• Cluster Communication Security - The scheduling engine encrypts network traffic between nodes and enforces authentication for storage backends and API access to protect sensitive data and system integrity.
• Job Lifecycle Management - Manages job lifecycles including one-off executions, automatic retries, and custom timeouts to ensure jobs complete as expected.
• Distributed Execution Coordinators - Assigns tasks to specific nodes using tags and streams results back to a central leader to ensure reliable processing across the network.
• Pluggable Storage Backends - Abstracts job persistence and cluster configuration into interchangeable drivers to support various distributed key-value stores or databases.
• Task Schedulers - Runs jobs across infrastructure using protocols including shell commands, HTTP requests, gRPC, or message queues to perform work on external systems.
• Execution Status Monitoring - The scheduling engine tracks job performance, execution times, and status through integrated dashboards, logs, and telemetry exports to gain visibility into system operations.
• Gossip-Based Cluster Membership - Maintains a dynamic list of healthy cluster nodes by exchanging state information through a peer-to-peer discovery mechanism.
• Distributed Task Coordination - A cluster-aware engine that coordinates remote task execution and maintains state consistency across multiple servers using pluggable storage backends.
• High Availability Clustering - Maintains a fault-tolerant system by electing leader nodes and scaling capacity to handle growing workloads dynamically.
• High-Availability Task Schedulers - Adds or removes nodes dynamically to increase the total volume of work processed and maintain high availability as demand grows.
• Plugin-Based Architectures - Extends system functionality by loading external modules that handle specific task types and communication protocols for remote job execution.
• Observability Platform Exporters - Exporting execution metrics, logs, and job status updates to external monitoring platforms to track performance and system health.
• Telemetry Exporters - The scheduling engine forwards internal metrics, traces, and logs to external observability platforms using standard protocols to track system health and job performance.
• Operational Task Automation - Executes shell commands, HTTP requests, or gRPC calls across remote systems to manage background operations programmatically.

Star history