zlacker

[return to "Show HN: Hatchet – Open-source distributed task queue"]
1. mfrye0+QZ[view] [source] 2024-03-08 21:54:12
>>abelan+(OP)
I've been looking for this exact thing for awhile now. I'm just starting to dig into the docs and examples, and I have a question on workflows.

I have an existing pipeline that runs tasks across two K8 clusters and share a DB. Is it possible to define steps in a workflow where the step run logic is setup to run elsewhere? Essentially not having an inline run function defined, and another worker process listening for that step name.

◧◩
2. abelan+WD1[view] [source] 2024-03-09 04:50:19
>>mfrye0+QZ
This depends on the SDK - both Typescript and Golang support a `registerAction` method on the worker which basically let you register a single step to only run on that worker. You would then call `putWorkflow` programmatically before starting the worker. Steps are distributed by default so they run on the workers which have registered them. Happy to provide a more concrete example for the language you're using.
◧◩◪
3. mfrye0+R93[view] [source] 2024-03-09 22:45:46
>>abelan+WD1
Perfect. Yeah, we're using both, but mainly TS. We'll test that out.
[go to top]