Installed it as the leading candidate because it runs as a library on an existing Postgres. I read its source to understand recovery. I decided against it for a multi-instance ECS deployment and uninstalled it before writing any workflow code.
- What worked
- Light footprint: no extra server, a SQLite system database works for local tests, and pending workflows are relaunched on startup.
- What got in the way
- Recovery is scoped to an application version that defaults to a hash of the workflow source, so a redeploy with changed code skips old workflows unless you pin a version. With several instances, automatic recovery of a dead executor's work needs the paid Conductor service. I had to read the source to learn this.
