Michael Staib explains the benefits of GraphQL over REST and demonstrates how to build a GraphQL API using Hot Chocolate.
GraphQL is a great way to expose your APIs, and it has changed the way we think about consuming data over HTTP. Not only does GraphQL give us the power to ask for exactly what we want, but it also exposes data in a way that is more aligned with the way we think about data.
Over the last two years, GraphQL has become more and more mainstream. The ecosystem has grown phenomenally, and major players like Amazon, Twitter, Facebook, and more are all committed to GraphQL.
But what is GraphQL? What are the benefits of using GraphQL it instead of REST?
Together, we will look at the core problems that we are facing with the traditional REST service layers, which still power most of the Web.
After we have a better understanding of GraphQL, we will explore how we can build a GraphQL API with Hot Chocolate on ASP.Net Core. We will look at Prisma filters and how we can get your existing infrastructure under this new service layer. We will merge data from different sources like you did not think was possible by using the power of the GraphQL resolver concept.
Check out more of our featured speakers and talks at
ndcconferences.comndccopenhagen.com/
Why it's here
2 people recommend this
What people say. Recommended by developers as an excellent introduction to GraphQL in .NET using the Hot Chocolate library.
M
u/Megasware128in r/dotnet • Recommends
On “Graphql-dotnet vs Hot Chocolate, which one to choose?”
…features throughout the whole stack from client to database is awesome. Also Strawberry Shake and Banana Cake Pop are great complimentary tools for calling your apis. If someone disagrees I would love to hear the great sides of using graphql-dotnet.
Edit: Here is the creator of Hot Chocolate talking about GraphQL in .NET (through Hot Chocolate): link to this video…