Read models vs. View models about php-ddd HOT 2 OPEN

I had always considered Read Models and View Model the same, they are just object to carry data to UI layer where the later can format those data for presentation.

from php-ddd.

Similar question by @cer:

Another #eventstorming question: Read Models are typically depicted as being consumed by humans. But arguably a command triggered by, for example, a policy needs a "Read Model". Thoughts ?

/cc @ziobrando @tPl0ch

@tPl0ch states:

I personally don't like the term read model. The important part is the decision that is taken, either by a policy or a human, and that the decision can be taken locally. To do this all the required information needs to be present. So maybe decision model would be a better name?

@ziobrando states:

Yep, totally on you on the rationale. Don’t know if that’s a compelling reason for a name change #Lazy. I just say “a read model is a decision support tool” ...decision model could be misinterpreted in some other ways, I am afraid.

• https://twitter.com/crichardson/status/1283114985275572224

from php-ddd.