PULSEQUEUE
A distributed workflow engine in Go — the project where I stop building apps and start building infrastructure.
It started as an excuse to understand what actually happens underneath the async abstractions every web app leans on. I had wired up enough queues and cron jobs as black boxes; I wanted to build one from the metal up and find out what exactly-once, on-time, survives-a-crash really costs.
A workflow engine in Go: a pool of concurrent workers pulling tasks off a persistent queue, with retries and backoff, delayed and scheduled execution, and at-least-once delivery that survives a worker dying mid-task. The near-term goal is correct single-node semantics under load; the longer arc is distributed coordination — leases, heartbeats, and a leader election so the same job never runs twice on two machines.
It is early and exploratory, and I am building it in the open — design notes, the things that broke, and what I got wrong about concurrency the first time.