query other actor at command handler of EventSourcedActor about orleankka HOT 2 CLOSED

I don't see any problems with having async command hander. It's absolutely valid.

If not, these are couple of workarounds I'm thinking of:

1. make warehouse a simple service with a synchronous call.
2. add an extra step with a checking actor

1. will block thread - bad
2. you're not awaiting Tell operation - bad, will blow in unpredictable ways

The EventSourcingActor is just a sample. You're free to bend it to the needs of your application. That's why I'm releasing it as just an example, not as part of the core. In fact, copy-pasting it into your codebase and poking it until it fits is highly encouraged 😄

Regarding async command handler. There is a DispatchAsync method that is able to call both sync and async message handlers in a uniform way. You will pay a completely negligible price on wrapping/unwrapping task result for sync handlers but that's just it.

Try this code:

protected override async Task<object> HandleCommand(Command cmd)
{
    var events = (await DispatchAsync<IEnumerable<Event>>(cmd)).ToArray();

    foreach (var @event in events)
        Dispatch(@event);

    return (object) events;
}

from orleankka.

Sounds good, thank you

from orleankka.