> customers don’t need or want all of the cruft inside the domain model and your DB… Why would the customer need to know about the cruft? The view/UI shouldn’t

> customers don’t need or want all of the cruft inside the domain model and your DB… Why would the customer need to know about the cruft? The view/UI shouldn’t be exposing what’s not needed. Same with the DB, frameworks like MyBatis put the mapping where it belongs.