There's a good argument that GraphQL can become the single SDL you use to define the API of many services written in many different languages. In this sense, it

There's a good argument that GraphQL can become the single SDL you use to define the API of many services written in many different languages. In this sense, it makes sense to write GraphQL and generate the language constructs; kind of an "outside->in" approach. If you're codegening your API from language constructs, the API will inevitably begin to use patterns that make sense in your language, not patterns that are universal to GraphQL or your entire system. That being said, I don't agree with it. I'm not a fan of GraphQL for inter-service communication; it makes sense at the internet API boundary, but once you're inside your service mesh I prefer something simpler and easier to test, like gRPC.