3 ms·
> Do not apply this pattern with a loose hand. Why especially this pattern ? I would say you shouldn't apply any pattern with a loose hand...
by je42 7y ago
> Do not apply this pattern with a loose hand.
Why especially this pattern ?
I would say you shouldn't apply any pattern with a loose hand...
- awinder 7y agobecause different patterns have different side effects and hence misapplying different patterns could yield different degrees of impact. Can’t speak for the parent commenter but cqrs can have nasty interplay between side effects. Commonly you would need to build interfaces that are aware of eventual consistency between read/write models, and your data scheme is definitely going to be impacted by the design choice. Versus misapplying an in-code pattern which might be an all-internals refactor to “undo the damage” it would take a lot to walk back a cqrs system.
- danielovichdk 7y agoIn my experience, when CQRS is applied to a system, top down, it fails to be a success. CQRS is not a system wide pattern. It should applied in small contexts and corners of domains. I don't agree that every design pattern has the same level of impact on a system. By far IMHO.
- je42 7y agoUsing Kappa architecture it becomes a system-wide pattern; and it should be applied in a large context; because thats the point of the architecture ;)