Michael is a Microsoft MVP and the author of the Hot Chocolate project (https://github.com/ChilliCream/hotchocolate), a platform for building GraphQL servers and clients in .NET. For the last three years, this open-source project is his main focus.
Apart from his work in the open-source community, Michael works as a consultant to help companies to move to GraphQL. You can read about the Hot Chocolate project on his blog https://chillicream.com/blog/.
GraphQL is a great way to expose your APIs and it has changed the way we think about consuming data over HTTP. With GraphQL we want to have one schema that provides all the data to us in a consistent way, enabling us to drill into the graph and fetch with one request what we actually want instead of having to issue multiple requests.
In the real world, however, we more often build small services that serve certain use cases. Simpler services are easier to maintain and can be deployed more rapidly. Moreover, we often also want to use external services that are not built by us. Ultimately, we will end up with multiple APIs again.
The solution for this dilemma is schema stitching. This talk will explore the schema stitching capabilities on ASP.Net Core with Hot Chocolate.
We will show how you can set up a Hot Chocolate GraphQL gateway in under 5 minutes and move on to the various stitching scenarios.
This talk introduces simple auto-stitching scenarios and goes on to demonstrate how you can rewrite your GraphQL APIs into something truly new.
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 actually? What are the benefits of using GraphQL it instead of REST?
Together we will have a 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 things like 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.
Blazor and GraphQL combined will revolutionize how we build rich SPA applications with pure .NET.
Blazor for the first time in years gives us .NET developers the ability to develop applications that run in the browser. This allows us to use our knowledge that we acquired in the backend or with desktop applications and use that in the web.
GraphQL on the other hand changed how we work with data fetching. With GraphQL the frontend developer defines how the interface between the frontend and the backend looks like. We no more have friction between backend and frontend developer and are able to iterate much faster.
Let us explore together how we can put those to together and change how we design components by binding them to GraphQL fragments. With GraphQL the data becomes front and centre and drives our application.
After having a fundamental understanding of how GraphQL improves our data fetching needs in web applications we will move on and build a nice real-time application with Blazor and GraphQL. Let us together build a truly engaging next gen application and push Blazor to the limit.