Happy to hear my answer helped you further @Beka_Tsotsoria. I definitely recommend taking a look at what @Oliver_Libutzki shared, as from the sound of it his solution would point you in the right direction too.
Now let me cover some of the follow-up in your most recent post:
Just wondering why
aggregateTypeis not part of the unique constraint anymore (as of Axon 3)?
I wasn’t a part of this decision back in the day, although I do recall this was indeed for performance reasons. Having the uniqueness constraint on three columns I assume proved to be less optimal for some/all (not sure here tbh) database implementations.
… but unfortunately AxonServer EE is not an option for me.
That’s a shame! Know that you can always contact AxonIQ directly to discuss the options out there. Although setting up MongoDb and Kafka yourself can be fun, remember you would also require another distributed command and query routing solution. You’d be required to move away from business functionality development towards infrastructure set up, which would not immediately benefit your company. Axon Server aims to resolve this pain for as much people as possible.
Regarding set-based-validation, I posted a question some time ago here, I’d appreciate your thoughts there as well when you have time.
Sure, I’ll have a look!