Re:A Brand New “Workflow as Code” Execution Engine
by rylandgold on Tuesday February 07, 2023 @08:59PM
(#34703126)
You can absolutely approach it that way, but AFAIK those are highly integrated but still discrete solutions. Temporal provides a unified model for these things instead of requiring people to stitch things together themselves. Due to Temporal handling all of the things, you also get additional value out of the centralization (you can see the live source of truth for any running business process).
I do agree that Temporal is heavyweight both in terms of the learning curve and deployment requirements.
For disclosure I’m the Head of Product at Temporaly. We know things can be better and we are working on it.
Re:A Brand New “Workflow as Code” Execution Engine
by johtso on Wednesday February 08, 2023 @12:40PM
(#34711665)
I can't wait for Temporal's cloud offering to work for the "small dev". It would be so wonderful to only need to worry about the learning curve of using the tool, and not the deployment + cost. It would be great to be able to reach for it for any little project that needed robust persistent workflows.
Re:A Brand New “Workflow as Code” Execution Engine
by rylandgold on Wednesday February 08, 2023 @02:41PM
(#34713707)
Completely and totally agree! Don't lose faith we will get there I promise.
cloudflare alarms seem like a decent solution for scheduling. If you want a state machine, you can just use a state machine (xstate).
The durable object primitives are more limited, but therefor seem a little easier to get your head around if you don't need all sorts of complex signalling.
introspection / analytics is obviously a pain to have to deal with yourself. I guess you'd end up saving the state to a database after any action. And you could probably get a reasonable little analytics dashboard fairly painlessly by chucking something like appsmith in front of it?