@elizarov if I have to pick between doing a globalscope launch vs launching a thread and inside that doing a withContext Dispatchers io launch - which one would be preferred? Context: cannot use run blocking on the calling thread and it is not a suspending function but want to launch multiple coroutines to do some stuff in parallel

You can just launch directly on the IO dispatcher from whatever thread.

val scope = CoroutineScope(<http://Dispatchers.IO|Dispatchers.IO>)
scope.launch { /* do blocking stuff */ }
scope.launch { /* do blocking stuff */ }
scope.launch { /* do blocking stuff */ }

Oh so great

Don’t forget to cancel the scope appropriately

Why would i cancel the scope?

To stop those coroutines and avoid leaking them when you don’t need them anymore. If you want them to run as long as your process is alive, you don’t need to cancel it.

Hmm. The coroutines are launched - they do some stuff and exit. Do i still have to cancel?

It’s good “hygiene” to clean up your scope, to prevent leaks (in case, for some reason, one of the coroutines doesn’t actually exit itself, or is still running when your scope is cleaned up)