ztick — Push-Driven Job Scheduler in Zig

Page not found

Mon, 27 Apr 2026 00:00:00 +0000

Sorry, we can’t find the page you’re looking for.

Use the navigation above or go back to the homepage.

0001: Hexagonal Architecture (Ports and Adapters)

Mon, 01 Jan 0001 00:00:00 +0000

Status: Accepted Date: 2026-03-28 Supersedes: N/A Superseded by: N/A

Context

The ztick scheduler needs a clean separation of concerns between business logic, adapters, and the interface layer to enable:

0002: Zig Language Choice

Mon, 01 Jan 0001 00:00:00 +0000

Status: Accepted Date: 2026-03-28 Supersedes: N/A Superseded by: N/A

Context

ztick is a time-based job scheduler that needs:

Fast compilation — Developers need tight feedback loops; CI must stay fast
Minimal dependencies — Reduce supply chain risk; audit the entire stack
Runtime simplicity — Single-threaded core with 3 helper threads; no need for complex async runtimes
Explicit memory control — Scheduler needs predictable, deterministic allocation
Small deployment — Binary should be self-contained, deployable to minimal environments

Candidates

Option	Pros	Cons
Zig	Blazing fast compile (2-3 sec); stdlib only; explicit allocators; minimal binary	Less mature; smaller community; no garbage collection
Rust	Mature ecosystem; strong type system; large community	Slow compile (30+ sec for similar projects); heavy dependency graphs; overkill async ecosystem for this domain
C	Extremely fast; minimal binary; portable	No type safety; manual memory is error-prone; no modern tooling
Go	Fast compile; solid stdlib; deployment story	Garbage collection (unpredictable latency); heavier binary

Decision

Build ztick in Zig (currently 0.15.2).

0003: System OpenSSL for Server-Side TLS

Mon, 01 Jan 0001 00:00:00 +0000

Status: Accepted Date: 2026-03-30 Supersedes: N/A Superseded by: N/A

Context

F006 adds TLS support to ztick’s TCP server (FR-001). This requires a server-side TLS implementation capable of accepting connections, performing handshakes, and wrapping streams.

0004: OpenTelemetry SDK Dependency for Instrumentation

Mon, 01 Jan 0001 00:00:00 +0000

Status: Accepted Date: 2026-03-31 Supersedes: N/A Superseded by: N/A

Context

F010 adds OpenTelemetry instrumentation to ztick (metrics, traces, structured logs). This requires OTLP/HTTP serialization, metric registry with atomic counters/gauges/histograms, span lifecycle management, and a dedicated exporter thread.

0005: AMQP Runner Design

Mon, 01 Jan 0001 00:00:00 +0000

Status: Accepted Date: 2026-04-26 Supersedes: N/A Superseded by: N/A

Context

F019 adds an AMQP 0-9-1 runner to ztick so that scheduled jobs can publish messages to a broker (e.g., RabbitMQ) as their execution action. Five independent design decisions shaped the implementation in src/infrastructure/amqp_runner.zig:

0006: Redis Runner Design

Mon, 01 Jan 0001 00:00:00 +0000

Status: Accepted Date: 2026-04-27 Supersedes: N/A Superseded by: N/A

Context

F020 adds a Redis runner to ztick so that scheduled jobs can publish to a Redis pub/sub channel, push onto a list, or set a key as their execution action. Five independent design decisions shaped the implementation in src/infrastructure/runner/redis.zig and the codec at src/infrastructure/redis/resp.zig:

Building the Project

Mon, 01 Jan 0001 00:00:00 +0000

Guide to compiling, testing, and packaging ztick from source.

Prerequisites

Zig 0.15.2 ( download)
libssl-dev (Debian/Ubuntu) or openssl-devel (Fedora/RHEL) — required for TLS support
git (optional, for cloning the repository)

Zig package dependencies (fetched automatically by zig build):

Configuration

Mon, 01 Jan 0001 00:00:00 +0000

This guide covers setting up and customizing ztick through TOML configuration files.

Configuration File Location

Specify the config file when starting ztick:

Configuration Reference

Mon, 01 Jan 0001 00:00:00 +0000

Complete specification of all TOML configuration options.

ztick is configured via a TOML file passed with the -c / --config flag. All sections and keys are optional; omitted values use the defaults below.