Getting started with GraphQL in .NET

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.

[eugenpaval]

Thanks for the presentation.! I am using HC and it completely changed the business where I am employed. What took minutes takes now milliseconds and what was hours is now measured at worst in tens of seconds. It's not only speed of execution, is the quality of the data, the response time to bring something new into the API as well. I aslo, wholeheartedly agrree with Michael's assertion that writing GraphQL with HC is easier than going REST. ChiliCream team, fantastic work, kudos!