Thanks for creating the channel. I wonder what are the best ways for architects to create flow?

Trying to decide if graphql-dotnet or apollo would be better for implementing a GraphQL api. Seems like the pros for graphql-dotnet for my org are that we can use .NET Core, C#, and EntityFramework, but a big con is that it doesn't seem to be widely tested in production? Pros for apollo are that it's OSS, it's more mature, it seems to be the most widely used platform for GraphQL APIs, which also makes me a lot more comfortable running it in prod. We have some experience with node and a good deal with JS of course, so I'm really leaning toward Apollo. Does anyone have experience with using either/both in a .NET shop? Maybe something else?

Trying to decide if graphql-dotnet or apollo would be better for implementing a GraphQL api. Seems like the pros for graphql-dotnet for my org are that we can use .NET Core, C#, and EntityFramework, but a big con is that it doesn't seem to be widely tested in production? Pros for apollo are that it's OSS, it's more mature, it seems to be the most widely used platform for GraphQL APIs, which also makes me a lot more comfortable running it in prod. We have some experience with node and a good deal with JS of course, so I'm really leaning toward Apollo. Does anyone have experience with using either/both in a .NET shop? Maybe something else?