The n+1 problem with graph representations of non-graph data is so common it begs for a solution in the core of the design, not as something added on or a "best

The n+1 problem with graph representations of non-graph data is so common it begs for a solution in the core of the design, not as something added on or a "best practice" like dataloaders. It worked for Facebook when they created GraphQL because they already had the backend shaping the data into a Facebook social graph. Everyone else is probably using relational data, and I have personal experience with the pain of manually coding around N+1 for every instance.