The would say that asynchronous methods are mostly about orchestration and side-effects and non-asynchronous ones about computations. If your computation code

The would say that asynchronous methods are mostly about orchestration and side-effects and non-asynchronous ones about computations. If your computation code reach out to fetch data or trigger side-effects I’d take that as a sign of it being badly factored. Try to push the async parts up the stack to an orchestration layer, and keep the computation code “pure”