In C# this would just be called a Repository pattern, and often you would handle caching externally, in a datatstore separate from your database or at the reque

In C# this would just be called a Repository pattern, and often you would handle caching externally, in a datatstore separate from your database or at the request layer (though there are obviously mature in-memory cache options). I haven't used GraphQL much but things like this make it seem that it's not a great general use case framework- if you don't really need it, save yourself from a bunch of extra logic in your application code.