New answers tagged

0

This approach appears to be frowned upon, given that most of the literature says that command handlers should not return domain data. There are a lot of conflicting ideas in the space, and you have to be a bit careful about which sets of ideas people are talking about. CQRS - the idea that we can have two data models rather than just one -- takes its name ...


2

This allows the client to update its representation of the affected resources, without having to perform a follow up query immediately The catch is in the implication here. What you're effectively saying is: I have to fire one less request when I merge the two requests (i.e. the command and subsequent query) into one. What you're saying is not wrong, but ...


4

CQRS is a principle, not a dogma. Like all principles, it has its positive and negative aspects in its own right. Departing from "pure CQRS" could just mean that you can't meaningfully call it CQRS. Quoting Martin Fowler: The really valuable idea in this principle is that it's extremely handy if you can clearly separate methods that change state ...


Top 50 recent answers are included