Automatically avoiding GraphQL N 1s | Aha!

Some people, when faced with an API problem, think “I’ll use GraphQL!” And now they have N 1 problems.N 1 problems occur when you want to find a deep tree of records and end up performing a SQL statement or API request for every record, instead of retrieving all records — or all records of a given type — at the same time.In Rails, N 1 problems are simple to solve using includes:.