Another worker vs. workflow for background work?
We need to vectorise some user input to our worker, and my idea was to have a separate worker, via a binding, that could do this task without holding up the main worker that receives user input and gives output. I can do this via
waitUntil(). However I just discovered Workflows and this sounds like much the same thing, suited to the task. Which would be better in my case and what are the key considerations?
Thank you.1 Reply
Anyone able to help here?