Most of the work that needs a durable engine is not glamorous. It is an expense waiting for a signature. A job that fails at 3 a.m. because a network cable sneezed. An order message that arrives twice. A batch whose size you only know when it starts.

These are the problems I had in mind while building Packtrail. Here are six ordinary workflows, each based on a runnable example in the repository, and what Packtrail does with them.

When I first wrote about Packtrail, the pitch was a single sentence: a durable workflow engine that needs nothing but NATS. No database, no coordinator, no second thing to keep alive.

Today that sentence gets a version number. Packtrail 1.0.0 is out.

The second time around

Here is the part I don’t usually put in a release post: version 1.0.0 is not the first draft with a nicer tag. It is the second attempt.