Flows on Go Micro

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.

When the Event Is the Prompt

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

Almost every agent demo starts the same way: a human types a prompt, the agent responds. That framing is a habit from chat, and it hides the more useful case. The agents worth running don’t wait for you to ask. They run because something happened — a user signed up, a payment failed, a deployment finished, a metric crossed a line. In those systems there is no prompt, because there is no human in the loop. The event is the prompt.

From Chat to Flows: What If Your Services Could Orchestrate Themselves?

Fri, 29 May 2026 00:00:00 +0000

We shipped micro chat recently — an interactive terminal where you talk to your services through an LLM. You say “list all users over 30 and send each a welcome email,” and the model figures out which services to call, in what order, with what arguments.

It works. But it’s interactive and ephemeral. You type a prompt, get a result, move on. What if you could save that prompt as a flow and trigger it from an event?