Command-Query Responsibility Segregation
Recorded at:
Re:
by
Maxim Tihobrazov
And the same question about lack of data in domain entities if we already store it in the views. Again we have to do some complex migration from query source to core data storage.
View database updates?
by
Dandik M
None the less, the thirst question that came from almost anyone who we presented the concept to was:
What about users editing theyr own account information? Let’s say user changes his address, closes browser and then remembers he forgot to change house number. It’s going to be frustrating if he opens his account information and bum – the information he just entered is not there (just because the view database is not yet up to date)!
Yes this might be a rear use case, but the frustration level as I can imagine might be … well let’s say high.
What I want to say, the concept is good as long as there are no data updates going on in the system. I can hardly imagine let’s say ERP system without updates, that needs to be reviewed right away after they are done. What is your solution to this scenario?
Slides
by
Ashwin Jayaprakash
Annoying tone
by
Wouter Vos
He may have interesting observations on current processes, but we're not stupid, it's not like he's unveiling a big secret here.
Good stuff
by
Dmitry Novoselov
And if we changed our minds and built another architecture, we wouldn't have to do all those tweaks. I'll definitely try to use more of this approach in my next project.




Hello stranger!
You need to Register an InfoQ account or Login to post comments. But there's so much more behind being registered.Get the most out of the InfoQ experience.
Tell us what you think