Yes, GraphQL is good and specification . There is also OData available way before and it's already used by Microsoft and other companies which provides similar features.
Unless you are building a complex View Aggregation Layer, I don't see a reason as not to at least take a look at OData before considering GraphQL. Pity you did not talk about it.
Wow, Excellent way of querying data over internet with no overfetching or underfetching. My Next PROJECT will use this.
Yes, GraphQL is good and specification . There is also OData available way before and it's already used by Microsoft and other companies which provides similar features.
Take a look stackoverflow.com/questions/50687332/odata-vs-graphql
Both have their own usecase, pros and cons.
this channel easily deserves more subs ...
This was very informative, expertly presented and delivered. Thank you very much!
32:10 if you're already convinced on GraphQL and want to get into the meat and potatoes of how to develop it in .NET
I would prefer the GraphQL to evolve a bit more before we start using it at least in .net
Evolve in what ways?
Unless you are building a complex View Aggregation Layer, I don't see a reason as not to at least take a look at OData before considering GraphQL. Pity you did not talk about it.
Nice video!!!
I find this talk quite chaotic and hard to follow.
She did fly thru a lot of material though. Pretty comprehensive for 1 hour.