prefect server in zig

archive
chaos
evidence
incidents
python-reference
reviews
scratch
concurrency-limits.md
database.md
deploy-ha.md
docker.md
docket-adoption.md
filters.md
migrations.md
operations.md
perf-zig-vs-python.md
profiling.md
README.md
ROADMAP.md
services.md
terminal.md
web-server.md
README.md

prefect-server internals #

zig implementation of a prefect-compatible server.

components #

  • terminal output — startup progress, log presentation, and terminal fallbacks

  • web server — HTTP, WebSocket routing, and optional UI serving

  • database — sqlite + postgres persistence

  • migrations — schema versioning strategy

  • services — background workers (broker-consumers + docket-driven loops)

  • docket adoption — how the loop services moved off threads onto docket, and why

  • operations — running production: deploys, drift, verification

  • HA deployment — 4-container compose (webapp + services + postgres + redis), scaling notes

broker and messaging details in src/broker/AGENTS.md and src/services/AGENTS.md.

performance #

  • perf-zig-vs-python.md — apples-to-apples benchmark across three topologies (local, single-container, containerized HA). includes correctness parity table, fairness disclosures, and reproduction recipe.
  • profiling.md — in-tree memory + load analysis rubric. /api/metrics surface, scripts/profile-load, and the discipline mirrored from zlay's ops changelog.

working notes #

  • scratch/ — working designs, unresolved investigations, and implementation references.

  • archive/ — historical plans and completed investigations.

  • chaos/ — bounded fault testing, production smoke checks, and retained evidence.

reference #

  • python-reference/ — how the python prefect server implements its database layer (SQLAlchemy, migrations, dialect differences).

incidents #

  • incidents/ — post-mortems. Incident narration lives here, not in AGENTS.md.

see also #

  • roadmap — implementation status vs python prefect.
  • changelog — chronological record of changes.