GraphQL is good at complex specificity. Leaving it to the caller how it wants its data structured in the return.
The struggle with it is more on the provider side. As you'd have horrible performance if you'd just rawdog an ORM onto it. The complexity of combining is where you'll struggle.
Last I played with GraphQL was with PHP. There is exactly one package that did GraphQL at that time. Where we had to define the models both in yaml and php.
Though this could probably be solved with dynamic building of the yaml.
Also last I checked the testing utils werent there yet.
Though it is really cool to be able to do supergraphs if you decide to do microservices.
Alternatives are json and protobuf. GraphQL kind of lands between big json blobs and protobuf's binary in size. Due to it's possible exactness. But that is wholly dependant on implementation.
The struggle with it is more on the provider side. As you'd have horrible performance if you'd just rawdog an ORM onto it. The complexity of combining is where you'll struggle.
Last I played with GraphQL was with PHP. There is exactly one package that did GraphQL at that time. Where we had to define the models both in yaml and php.
Though this could probably be solved with dynamic building of the yaml.
Also last I checked the testing utils werent there yet.
Though it is really cool to be able to do supergraphs if you decide to do microservices.
Alternatives are json and protobuf. GraphQL kind of lands between big json blobs and protobuf's binary in size. Due to it's possible exactness. But that is wholly dependant on implementation.