kestrel
kestrel copied to clipboard
Suspend functions in aggregates & event processors?
I was surprised that neither functions for aggregate creation/updates nor event processor updates are marked as suspend
.
I assume that this was a conscious decision - do you have some background about it? Especially interaction with databases to update aggregates is bound to use suspend
ing I/O. For the time being, we're thinking about explicitly launching jobs on Dispatchers.IO
and manually waiting for them to complete - but using suspend
functions would probably be more concise.