title: Full fat or skinny DTO objects?
body: <p>Do I want to return Full-Fat Dtos; i.e. with basic parent entity info, it's Id and name, and collections of child entities converted to collections of child dtos; or strip everything back and only return ids for parent entities?</p>
  
  <p>The skinny choice will appear result in lots of calls back to the web-api to fill in the missing details, but the full-fat dto will be a fairly heavy object if an entity has many child, grand-child, etc relationships.</p>
  
  <p>Is there a semi-skimmed option to halt dto serialization at a certain level?</p>
  
  <p>To add some additional context: we are wrapping a 3rd party api for internal use. The 3rd party is using the "skinny" approach to return ~18,000 entities, about 18mb.</p>
  
  <p>For this to be anything more than a collection of ids we need add at least some context. Id and Name entities are simple enough to include but where the related fields may have child relationships which due to underlying database design lead to interesting circular relationships things get interesting...</p>