title: Why should I isolate my domain entities from my presentation layer?
body: <p>One part of domain-driven design that there doesn't seem to be a lot of detail on, is how and why you should isolate your domain model from your interface. I'm trying to convince my colleagues that this is a good practice, but I don't seem to be making much headway...</p>
  
  <p>They use domain entities where ever they please in the presentation and interface layers. When I argue to them that they should be using display models or DTOs to insulate the Domain layer from the interface layer, they counter that they don't see the business value in doing something like that, because now you have a UI object to maintain as well as the original domain object.  </p>
  
  <p>So I'm looking for some concrete reasons I can use to back this up. Specifically:</p>
  
  <ol>
  <li>Why should we not use domain objects in our presentation layer?<br>
  (if the answer is the obvious one, 'decoupling', then please explain why this is important in this context)</li>
  <li>Should we use additional objects or constructs to isolate our domain objects from the interface?</li>
  </ol>