go-workflows
go-workflows copied to clipboard
Embedded durable workflows for Golang similar to DTFx/Cadence/Temporal
It would be nice to support different queues for activities. That way a worker could process only specific activities.
For a scenario like: ```go func SubWorkflow(ctx workflow.Context) (int, error) { ... } func Workflow(ctx workflow.Context) error { x, err := workflow.CreateSubWorkflowInstance[string](ctx, ..., SubWorkflow).Get(ctx) } ``` it would be good...
The integration tests take quite a bit of time to run. As a start, they could be split into separate actions jobs to run e.g. Redis and MySQL integration tests...
For telemetry purpose, it's useful to have access to the current "call stack" of workflow, sub workflow, activities and so on, at any given point. For instance, to make better...
## SQL backends Instead of duplicating events in the `history` and `pending_events` table, events should be stored in a single `events` table. `history` and `pending_events` should contain only references to...