Menu
I found GraphQL as an enticing option to decouple front-end development from APIs (potentially a great fit for our company, which does lots of API customization for each customer). However, I can't quite work out if it's ready for a .NET development environment, or whether it's still considered an early technology? I also can't tell if it has bigger problems under the covers (e.g. N+1 issue). Any experience and guidance for GraphQL with a .NET implementation?
363
GraphQL does not provide any direction for how to store data or what programming language to use—developers can use PHP (graphql-php), Scala (Sangria), Python (Graphene Python), Ruby (graphql-ruby), JavaScript (graphql. js), and more. GraphQL offers no requirements for the network, authorization, or pagination.
GraphQL allows for content negotiation which means you will only have one endpoint. It also allows you to query for exactly the fields you want. On the backend, you can grab the data from different data sources so there definitely is a good reason to be excited, for frontend developers as well as backend developers.
The fact that there is no answer here after one month should tell it's tale.
I have shifted my focus from .NET Framework to .NET Core and after trying out the .NET libraries available, I soon went for an API gateway built on TypeScript and the more mature Facebook supported GraphQL implementation.
With the server issue solved, my combined .NET Framework/Core based client easily communicates with the API gateway. As the gateway itself is rather lightweight, exchanging this for a more solid .NET Core implementation later will be easy.
50
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
