Design patterns·Modelling the domain
the object crossing the boundary has fields matching the screen, not the model, and no behaviour at all.
Data transfer object
Also calledDTO, transfer object, response model
A simple carrier of data across a process or layer boundary, shaped by what the consumer needs rather than by the domain. Its original purpose was to reduce the number of remote calls by batching everything the caller needed into one object, and its lasting purpose is to stop the domain model becoming a serialisation format. It looks like an anaemic domain object and is not one, because it was never meant to have behaviour.