Sagas on FlowChassis.com

What a Workflow Execution Kernel Is and Why Sagas Need One

Sun, 18 Oct 2026 00:00:00 +0000

Picture an online shop’s order code. Reserve the stock. Charge the card. Print a receipt. Book the courier. Email the customer. Five calls, five different systems, and no database transaction that spans them, because the card network and the courier don’t take part in your transactions.

Most of the time all five work. The trouble is the other times. The courier’s API refuses the address after the card was charged. Or the server restarts during the charge, and nobody knows whether it went through. Each of those leaves the order half done, and half done is the worst state there is: money taken, nothing shipped, and the code that knew what to do next gone with the process.

Account Signup With FlowChassis Leaves No Half-Made Accounts

Sun, 18 Oct 2026 00:00:00 +0000

Signing someone up sounds like one action. It’s usually four. You create the user record, give the account its storage, send the welcome email, and switch the account on. Each of those talks to a different system, and any of them can fail while the others have already happened.

The usual result is a half-made account. The user row exists but the bucket doesn’t. Or the bucket exists, the email bounced, and nobody knows whether to try again. Someone writes a cleanup script. Then the cleanup script needs its own cleanup.

Cloud Provisioning With FlowChassis Tears Down What a Failed Deploy Built

Sun, 18 Oct 2026 00:00:00 +0000

Putting a site on a new server takes a handful of calls to different providers. Create the VM. Point a DNS record at it. Get a TLS certificate. Then wait until the thing answers its health check, which can take a while because VMs take time to boot.

When the certificate step fails, you’re left with a VM you pay for by the hour and a DNS record pointing at it. Run that a few hundred times across a team and you get the cloud bill everyone recognises: servers nobody remembers creating.