Yesterday, I walked around Sakura City to visit a museum and heard a chime; I quickly recognized it as “Goin’ Home”. It was probably my first time hearing it as a chime but somehow I felt a little bit nostalgic.
I learned which situation causes the N+1 problem while implementing a GraphQL server with gqlgen. Here are the key points. Splitting resolvers To avoid over-fetching from the DB, we can set resolver: