“CQRS is actually in danger of reaching “best practice” status at which point in time people will apply it indiscriminately with truly terrible results.”
One does get this impression by the amount of material out there on the subject. It’s easy to see why this is the case. Here are the driving forces from your previous blog entry:
“Collaboration refers to circumstances under which multiple actors will be using/modifying the same set of data”
“Staleness refers to the fact that in a collaborative environment, once data has been shown to a user, that same data may have been changed by another actor – it is stale.”
The problem is an argument could be made that both of these driving forces were true for all of the applications (client side and web) I have built over the last 10 years.
I haven’t implemented CQRS or looked at a sample app as of yet, just doing alot of reading and trying to wrap my head around when to apply it. Great articles….
Cheers
