We hear about GraphQL as being the coolest kid in town, developed by Facebook and loved by the front-end developers.
With a REST API, you won’t need something else, but we all know that the apps consuming these APIs tend to suffer from overfetching and underfetching, and when we think about mobile apps, that is a major flaw.
Some say these APIs are badly designed, but what happens when you have little to no control over how your API is consumed?
In this session, we will talk about GraphQL in .Net, the why and the what, the pros and cons of using it and what it brings to the table.
Is it worth it? Is it just another buzzword?