Home

So, here's the trade-off: adding embedded objects can reduce the number of extra HTTP requests required to render the page of objects. For example, if showing a `followers` collection, adding each actor's name, avatar, and so on can be a real savings.

However, it puts a lot of costs on the server -- looking up cached or local data about each object.

Long story short: adding embedded objects is a pressure towards having smaller page sizes.

If you're not showing embedded objects, then filling up a collection page is usually just a couple of database queries. And adding more items to the page has very little extra cost.

The bigger your pages are, the fewer requests a client has to make to get all the data.

So, I think if you're not doing embedded objects, the pressure is towards bigger pages.