Hello! I’m a Husband, Father, Movember & Liverpool Fan, Software Engineer, Constant Learner & Team Leader. I live in Wisconsin, work for Catalyst and spend my days trying to balance all of the above.
@drminnaar This is a great post! You might want to break it up into a couple of posts and use the series feature on here to make it a little more digestible.
I've been playing around with GraphQL and .NET myself. Have used the alternative option GraphQL.NET but am about to pick up Hot Chocolate to build it again using that library. This will be a big help.
It's a cool tech but definitely needs some high level control from the engineers building it. Don't want to smash the database on every frontend request. That's how you spend mega dollars in the cloud by accident
Thanks @stphnwlsh, using a series is a great suggestion.
The support for GraphQL has improved a lot from its humble beginnings. Much respect to the builders that are working on these projects. The Chillicream offerings (both client and server) are looking more solid with every release. The latest version of HotChocolate has some good performance improvements too. I also like that you can use different approaches like code-first vs annotation-based vs schema-first.
Hello! I’m a Husband, Father, Movember & Liverpool Fan, Software Engineer, Constant Learner & Team Leader. I live in Wisconsin, work for Catalyst and spend my days trying to balance all of the above.
Yeah it's only getting better and I think .NET is becoming more viable for GraphQL systems.
Code first approach seems nice to me. I prefer the models being returned to have some decent decoration/detail to them for a better user experience consuming the API. Plus not a difficult upgrade on my existing solution
I like your approaches on GitHub too. Keep making good stuff!!!!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
@drminnaar This is a great post! You might want to break it up into a couple of posts and use the series feature on here to make it a little more digestible.
I've been playing around with GraphQL and .NET myself. Have used the alternative option GraphQL.NET but am about to pick up Hot Chocolate to build it again using that library. This will be a big help.
It's a cool tech but definitely needs some high level control from the engineers building it. Don't want to smash the database on every frontend request. That's how you spend mega dollars in the cloud by accident
Thanks @stphnwlsh, using a series is a great suggestion.
The support for GraphQL has improved a lot from its humble beginnings. Much respect to the builders that are working on these projects. The Chillicream offerings (both client and server) are looking more solid with every release. The latest version of HotChocolate has some good performance improvements too. I also like that you can use different approaches like code-first vs annotation-based vs schema-first.
Yeah it's only getting better and I think .NET is becoming more viable for GraphQL systems.
Code first approach seems nice to me. I prefer the models being returned to have some decent decoration/detail to them for a better user experience consuming the API. Plus not a difficult upgrade on my existing solution
I like your approaches on GitHub too. Keep making good stuff!!!!