Verifying Temporal Suitability for Synchronous Orchestration

I have a complex workflow in my current application involving a SOAP call, a REST call, a DB access, etc that all need to happen synchronously as the result of a call from a browser UI. Naturally, any of those side effects can fail, so I would like the normal infrastructure like retries, etc to be in place to be as fault tolerant and “transactional” as possible.

Is Temporal a suitable solution for this? It certainly seems so, but I ask because the docs seem very adamant that Temporal is geared towards async workflows and sync workflows are so unorthodox as to almost be a bad (even if technically supported) idea.


Is Temporal a suitable solution for this?

Yes, you can definitely define a sequence of sync activity executions in your workflow code.

1 Like