3 ms·
I think many people just dislike DDD and CQRS/ES because it's associated with over engineering. Either you are really good and get things right without much he
by k__ 9y ago
I think many people just dislike DDD and CQRS/ES because it's associated with over engineering.
Either you are really good and get things right without much help, which isn't often the case, or you end up in two other directions.
You over-engineer with DDD/CQRS/ES.
You under-engineer without them.
Most developers I met preferred the last solution, probably because they end up with their "own" mess and not the mess of some process.
And I have to admit, the only people I met, that used these techniques, were some "digital transformation" consultants who made their living by selling this stuff to big corps, which isn't too convincing either.
- ptr 9y agoFor some projects, ES isn't over-engineering. It can be useful when writing to a database is too slow, for example.
- naasking 9y ago> You over-engineer with DDD/CQRS/ES. CQRS/ES definitely seems like a correct foundations for a distributed system, I just don't think we have the right abstractions to properly model this without wanting to stab yourself in the eye.