A few reasons they don't cover that sort of thing in articles like this imo: 1. Graphql brought back n+1 problems for many popular frameworks/languages 2. Thi

A few reasons they don't cover that sort of thing in articles like this imo: 1. Graphql brought back n+1 problems for many popular frameworks/languages 2. This article's goal is to convert readers into paying customers, never forget that. Engineers at shops with large scale systems and problems like what you've outlined are not who will be reading this article and are not people who would pay for appsignal. They likely have existing performance monitoring systems that are either too specific to their systems, too entrenched into their infra, or more advanced for their needs. In the end this article is marketing, and effective marketing casts the widest net to get as many people into the funnel as possible. When you look at it that way, common scaling problems, like n+1 is going to buy more customers for the cost of this marketing campaign compared to the hyper-niche pool of shops worried about decoupling database:api 1:1 mappings