AllocDB – A deterministic resource-allocation DB built with Codex

Name: AllocDB – A deterministic resource-allocation DB built with Codex
Availability: InStock
Author: skel84

by skel84·Mar 16, 2026·1 point·0 comments

Visit Project View on HN

AI Analysis

●●●BangerBig BrainWizardryNiche Gem

First-class allocation primitive beats Postgres row locking for reservation systems.

Strengths

•Jepsen harness with 15-scenario matrix proves serious distributed systems testing discipline
•Zero-allocation hot paths in Rust for allocation-free steady-state after startup
•Deterministic WAL plus snapshot guarantees reproducible state across crash recovery

Weaknesses

•Early stage with no production deployments or real-world adoption metrics yet
•Competing against established distributed databases like FoundationDB and etcd

Post Description

Hi HN,

I’m a DevOps engineer who wanted to test whether an LLM could build high-quality systems code if guided by a strong architectural mental model?

I guided Codex to build AllocDB (a "one resource, one winner" database) using TigerStyle principles—strict determinism, zero-allocation hot paths, and logical time.

Because I didn't trust the AI (or my own coding skills), I had it build a Jepsen harness using my homelab's KubeVirt infrastructure to "bully" the database into failing. After a number of iterations, it now passes a 15-scenario Jepsen matrix.

Would love to hear from the community if this is interesting to you, and if you have any suggestions for how to improve the system or the testing harness!