Comments by "xybersurfer" (@xybersurfer) on "CQRS pitfalls and patterns - Udi Dahan - NDC Oslo 2023" video.

he should have explained the details of the underlying problem better. also a poor explanation of CQRS
18
@wealcome_company then the presenter really should have used a better example, than a ticketing system. i'm concerned with people like you that already think they have a solution, to a problem that was never fully explained. his compromise of not being able to choose the seat, doesn't even work for all ticketing systems like when children and parents are involved. i would have expected him to allow the user to specify that the seats have to be adjacent. i would have at least expected him to explain what the hell he was doing in the critical section, that took so long. without a good detailed example, it's all speculation
8
@KelvinMeeks he never described the underlying details of the problem. it happens too often that people wildy varying interpretations of what the problem is. i was also not happy with his explanation of CQRS, where he makes it sound as if it's impossible to base a write on a read operation
6
yeah he should have explained that better. maybe it somehow decreases what has to be done during a lock. who knows. it's a shame that he didn't go into more details about the actual underlying problem
3
@andredesantacruz this sounds like a trick question, but i'll answer: he talks about command and query separation, but a command often requires a query. i think that he should have explained this point of contention better, so that it at least sounds feasible
1
@andredesantacruz i think you are mixing up 2 different discussion topics: - was the presenter's explanation of CQRS good? - what is CQRS? i've only been talking about the first. when i answered your question, i was only using what the presenter has said. i did not make any claims about what CQRS is. you say that commands and queries are not related, but this does not make sense either. are you claiming that the output of the queries are not affected by the commands? if we continue this discussion you will probably provide a better explanation about what is CQRS (second topic) than the presenter, but my point (first topic) still stands.
1
@michelvandenberg7442 i did not know he was one of the first to coin CQRS. it's useful to know. by the way, i'm completely new to CQRS, but no to developing. i may do a deeper dive at some point
1
i don't know his other presentations, but i disagree
1