no, the whole point of temporal is to distribute work across machines, but without worrying too much on the orchestration.

workflows and activities are called remotely, and you can have an autoscaled worker pool handling these calls.

you can retry any unit easily on failure and specify the non retryable errors. What it requires in exchange is full determinism - the same input should produce the same activities in the same order, as a good starting point.

src: I'm a user since over a year ago.

Threads are durable nor distributed.