The design decisions behind djob
The reasoning behind djob's replicated coordination, independent workers, shared-resource reservations and release selection, with a worked capacity model and explicit recovery costs.
Follow a thread
The reasoning behind djob's replicated coordination, independent workers, shared-resource reservations and release selection, with a worked capacity model and explicit recovery costs.
Keeping Go services understandable and testable, so another engineer can change them safely and review work delegated to a coding agent.
Comparing Temporal, Dapr, two HTTP job schedulers and djob through research-based criteria, then following a gateway job through execution, uncertainty and recovery.