Doesn’t it seems like a valid use case where when an event is triggered it should trigger other commands in action in a persistent entity IMPLICILTY?
I understand that we could have a event listener which can again send a follow up command to the persistent entity. This however seems like a lot of boilerplate to me. A PersistentEntity actor may always end up having a listener for such uses cases!
Let’s say releasing an employee should trigger cancelling leaves “implicitly” in a leave management domain?
How about sending ReleaseEmployee and CancelLeaves to the persistent entity actor one after the other? How can we do that?
Is there any better to achieve this? What are design practices around this?