Top all-time · #10091
ChilliCream
Company blog · chillicream.com/blogprogrammingweb
ChilliCream is the company blog at chillicream.com, writing about programming and web. Since 2021, 8 different Hacker News readers have linked it 9 times, most often “Hot Chocolate: open-source GraphQL C# Server”. It is still writing: the last post was on 2026-08-03, and you can follow it by feed.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN commenters link ChilliCream's Hot Chocolate documentation, its .NET GraphQL server, for persisted queries and the MongoDB integration. None of the comments judge the writing itself.
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Build, federate, observe, and evolve GraphQL APIs on .NET with open-source Hot Chocolate, Fusion, Strawberry Shake, and Mocha, plus the Nitro control plane.
Most-linked posts?
- Hot Chocolate: open-source GraphQL C# Server2 people · 2 mentions · first linked 2022-01-06
What Hacker News says?
Yeah, we use Hot Chocolate with .NET where it is called Persisted Queries. https://chillicream.com/docs/hotchocolate/v13/security Honestly most of the "problems" the OP discusses has solutions in the documentation.
Comment linking /docs/hotchocolate/v13/security
on “After 6 years, I'm over GraphQL”Submitted GraphQL wasn't made for AI. But it might be one of the best ways to talk to it as a story · 4 points
HN discussionIIRC correctly, you may run into service scope issues if you just use a Mongo collection as an IQueryable directly, but there is a first class integration for Mongo from Chillicream: https://chillicream.com/docs/hotchocolate/integrations/mongo...
Comment linking /docs/hotchocolate/integrations/mongodb
on “Performance Improvements in .NET 6”Submitted Hot Chocolate: open-source GraphQL C# Server as a story · 2 points
HN discussionThe ability to pick fields is nice, but the article failed to mention GraphQL's schema stitching and federation capability, which is its actual killer feature that is yet to be seen from any other "RPC" protocols, nix the gRPC which is insanely good for backend but maybe too demanding for web, even with grpc-web *1. It allows you to separate your GraphQL in multiple "sub-graphs", and forward them to different micros…
Comment linking /docs/hotchocolate/v15/integrations/entity-framework
on “GraphQL: The enterprise honeymoon is over”Submitted HotChocolate: Open-source GraphQL server for .NET as a story · 2 points
HN discussionI've found the opposite. Designing a GraphQL API with the extended tail of important features has been an awful lot harder than with REST Apis. That's not just in terms of idioms (which are useful for abstraction layer sake), but authorization, performance, all the sorts of things that are very known quantities, with extensive framework integration, in REST land. You get a lot farther with the wide ecosystem of trac…
Comment linking /blog/2020/03/18/entity-framework
on “GraphQL Conf. 2021”Submitted Hot Chocolate: open-source GraphQL server for .NET as a story · 1 points
HN discussion