> here's access to anything you need - go ahead and use it however you need But that's almost never what you want: as the backend developer, it's one's job to

> here's access to anything you need - go ahead and use it however you need But that's almost never what you want: as the backend developer, it's one's job to care about security and the performance of queries. As far as I know there's no straightforward way of automagically translating every possible permutation of SQL query primitives into GraphQL primitives in a way that is intuitive to a frontend developer, reasonably performant and secure, so at some point the backend dev has to step in and do the work of connecting the GQL layer to the SQL layer.