If graphQL makes your backend 10x harder to develop, then you are not doing it right. The overhead of GraphQL vs Rest on a backend is around 30lines of code in

If graphQL makes your backend 10x harder to develop, then you are not doing it right. The overhead of GraphQL vs Rest on a backend is around 30lines of code in my experience (developed 5 different production Graphql servers, including a very large one). Routes become resolvers, but that’s mostly the only change. But in the end you get a much nicer API, GraphQL codegen, type safety, auto generated docs, etc...