Absolutely, if you're building a GraphQL server, parsing is almost certainly not your bottleneck. Stellate is effectively a GraphQL CDN, so for us, it is.
Our request flow effectively boils down to:
1. Parsing a GraphQL query to assess which types and fields are within it
2. Matching the configured cache rules to those types and fields
3. Caching partial results accordingly
So, for our specific use case, parsing is one of the main things our edge gateway does, and reducing overhead there allowed us to significantly improve our overall performance.
It was posted by the tech reporter at NPR. Inb4 “journos can’t be trusted” blah blah blah, here in reality NPR is a reputable org and a reasonable person’s Bayesian priors would put this at “almost certainly an actual statement from ScarJo.”
Variety has a story.[1] It doesn't yet mention an direct statement from Johannson. But watch that space. Variety is well connected in Hollywood and will check with her agent to confirm or deny.
Variety article updated: [UPDATE: Johansson released a statement saying Altman had reached out to ask her to lend her voice to ChatGPT but she declined; when she heard the demo, “I was shocked, angered and in disbelief that Mr. Altman would pursue a voice that sounded so eerily similar to mine.”]
> Default GQL encoding is redundant and we care a lot about limiting size because many of our customers have low bandwidth
I'd love to know how you ended up combating this! I'm assuming something like graphql-crunch[0] or graphql-deduplicator[1], but I'd love to know what worked well in practice.
I feel like this title is misleading compared to the original article. (cc @dang) Fly.io without cold starts (which is a one-line configuration change) is 2x faster than Cloudflare Workers.
Ok, we've changed to the article's title now, in keeping with the HN guidelines: https://news.ycombinator.com/newsguidelines.html. (Submitted title was "Hono on Cloudflare Workers is 3x faster than alternatives")
Submitters: If you want to say what you think is important about an article, that's fine, but do it by adding a comment to the thread. Then your view will be on a level playing field with everyone else's: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so...
I think it depends on your use case. If you want serverless — well, yes! You want it to scale down to zero and scale up to infinity really fast. Cloudflare Workers are really good at that.
On the other hand, if you want lowest possible latency, and the ability to run normal Linux applications (rather than being confined to the Cloudflare Worker limits, e.g. maximum worker size is 10MB), something like Fly.io is pretty nice: it's even lower latency than Cloudflare assuming you keep the machines running, and scaling up/down is relatively quick although not something you'd generally be doing every few seconds.
My quests (goals) with this digital garden are:
1. Publish more than I did when I just had space for essays, which hopefully leads to…
2. Getting more input from people on my ideas
3. And have fun futzing with my digital garden technically
So far, so good!