Durable Workflows

Wed, 17 Jun 2026 00:00:00 +0000

A workflow that calls real services is rarely instant and rarely side-effect-free. It reserves inventory at step one, charges a card at step two, sends a confirmation at step three. Each of those changes the world. So when the process dies between step two and step three — a deploy, an OOM, a node going away — you can’t just run it again from the top: that reserves twice and charges twice. And if the workflow was triggered by an event with no human watching, nobody noticed it died at all.

Not Everything Should Be an Agent

Mon, 08 Jun 2026 00:00:00 +0000

The last two posts were about agents — the abstraction, and then agents that plan and delegate, directing their own work over many turns. That’s the exciting part. It’s also, honestly, the part you should reach for least often.

An agent decides its own path at runtime. That’s powerful when the task genuinely needs it, and a liability when it doesn’t — you trade predictability, latency, and cost for flexibility you may not want. Most real work has a known shape: when this event happens, do these things. For that, you don’t want a model improvising. You want a workflow.

Workflows on Go Micro

Durable Workflows

Not Everything Should Be an Agent