zlacker

[return to "Show HN: Hatchet – Open-source distributed task queue"]
1. Kinran+6z[view] [source] 2024-03-08 19:37:21
>>abelan+(OP)
With NATS in the stack, what's the advantage over using NATS directly?
◧◩
2. abelan+2F1[view] [source] 2024-03-09 05:06:27
>>Kinran+6z
I'm assuming specifically you mean Nex functions? Otherwise NATS gives you connectivity and a message queue - it doesn't (or didn't) have the concept of task executions or workflows.

With regards to Nex -- it isn't fully stable and only supports Javascript/Webassembly. It's also extremely new, so I'd be curious to see how things stabilize in the coming year.

◧◩◪
3. rapnie+2X1[view] [source] 2024-03-09 09:58:47
>>abelan+2F1
I recently found Nex in the context of Wasmcloud [0] and ability for it to support long-running tasks/workflows. Impression that indeed Nex needs a good time to mature still. There was also a talk [1] about using Temporal here. For Hatchet it may be interesting to check it out (note: I am not affiliated with Wasmcloud, nor currently using it).

[0] https://wasmcloud.com

[1] https://www.temporal.io/replay/videos/zero-downtime-deploys-...

[go to top]