I have a command that not always need to create a new Aggregate.
If it already exists, it should just load the existing.
If it doesn’t exists, it should create a new one first.
How to handle these types of commands? I guess this is not possible with an @CommandHandler annotation on the aggregate’s constructor?
Do I have to create an “external commandhandler”?
If yes, how does this look like? Is this handler thread safe?