Workflow orchestrator in Golang
A brief overview: 1. Workflows steps share a running context, with access to data they need require. 2. Steps in the workflow (builders) are chained together based on a topologically sorted built from the predefined input & output. 3. No servers spin up (like Conductor/Cadence) - the orchestrator is low level and meant for simplifying business logic. 4. Before/After listeners for each step. Would love to hear your thoughts and feedback!
In plain words
This Golang workflow orchestrator chains together execution steps that share a running context, with automatic ordering based on input and output dependencies. Unlike server-based systems such as Conductor or Cadence, it runs as a lightweight library designed to simplify business logic without infrastructure overhead. It includes before and after listeners for each step, allowing developers to hook into workflow execution at key points.
written from the facts on this page · September 2026
More work this month
the category →
The app store for voice native apps that lives in your notch
Work · 28d ago · voiceos.com
The New Calendly▲211Handle all of the work before, during, and after meetings
Work · 17d ago · calendly.com
Launched alongside, March 2024
the whole month →
- 3Y
Life & fun · 2024 · github.com
Microlaunch▲1,116Launch and get feedback on both the idea and product
Dev tools · 2024 · microlaunch.net
