The problem that I’ve seen a bunch of times with the similar lazy-autoload approach in .NET Entity Framework is that someone accidentally/naively serializes one of the EF objects rather than projecting it to a POCO first, and then Prod blows up when the serializer dutifully follows all the relationships in a complex nested object and ends up pulling a massive amount of data from the DB and then tries to log/send 1GB objects at N requests per second. Oops