title: REST API and eager loading rested resources
body: <p>Imagine a resource such as Authors. An Author has multiple books, multiple pictures, etc.</p>
  
  <p>In some pages of my app, I only need the surface author data such as name. In other pages, I need all the nested resources as well. How do I handle the loading of nested resources? </p>
  
  <ol>
  <li><p>Do I load everything in one call such that: <br>
  GET /authors returns {
     name: x,
     books: {
       bookname: a,
        ...
     }
   }</p></li>
  <li><p>Accept an optional parameter that specifies the nested objects, such as: <br>
  GET /authors?include=books&amp;pictures</p></li>
  <li>Return just the surface author data then fetch the related resources in subsequent calls. However, this could lead to n+1 type queries, such as: <br>
  GET /authors <br>
  GET /author/1/images<br>
  GET /author/1/books</li>
  </ol>
  
  <p>Any insight appreciated</p>