CQRS and validations
I’m starting to introduce myself in CQRS concepts, but I get stucked with the following situation:
Supouse you have an entity that must have an unique name. In order to verify that, prior to create the entity you must make a query, thus you are verifing against the query subsystem.
But what happens if the syncronization has not been happened between the command system and the query system yet? Other client just had sent the same name before you.
What happens in that case?
CQRS and validations
I’m starting to introduce myself in CQRS concepts, but I get stucked with the following situation:
Supouse you have an entity that must have an unique name. In order to verify that, prior to create the entity you must make a query, thus you are verifing against the query subsystem.
But what happens if the syncronization has not been happened between the command system and the query system yet? Other client just had sent the same name before you.
What happens in that case?
CQRS and validations
I’m starting to introduce myself in CQRS concepts, but I get stucked with the following situation:
Supouse you have an entity that must have an unique name. In order to verify that, prior to create the entity you must make a query, thus you are verifing against the query subsystem.
But what happens if the syncronization has not been happened between the command system and the query system yet? Other client just had sent the same name before you.
What happens in that case?
CQRS and validations
I’m starting to introduce myself in CQRS concepts, but I get stucked with the following situation:
Supouse you have an entity that must have an unique name. In order to verify that, prior to create the entity you must make a query, thus you are verifing against the query subsystem.
But what happens if the syncronization has not been happened between the command system and the query system yet? Other client just had sent the same name before you.
What happens in that case?
Should we call a command inside another command in CQRS?
I know there are many posts on this question but none of them gives a clear answer or solution (atleast for my specific case)
Where should an object in CQRS+ES be fully initialized: in the constructor, or when applying the first event?
There appears to be widespread agreement in the OOP community that the class constructor should not leave an object partly or even fully uninitialized.
Where should an object in CQRS+ES be fully initialized: in the constructor, or when applying the first event?
There appears to be widespread agreement in the OOP community that the class constructor should not leave an object partly or even fully uninitialized.
Where should an object in CQRS+ES be fully initialized: in the constructor, or when applying the first event?
There appears to be widespread agreement in the OOP community that the class constructor should not leave an object partly or even fully uninitialized.
Domain Services vs. Factories vs. Aggregate Roots
After dealing with DDD for months now, I’m still confused about the general purposes of domain services, factories and aggregate roots in relation to each other, e.g. where they overlap in their responsibility.
Designing a social network with CQRS, graph databases and relational databases in mind
I have done quite an amount of research on the topic so far, but i couldn’t come up with a conclusion to make up my mind.