Lessons learned from running GraphQL • Hacker News Board

Re: Lessons learned from running GraphQL

#61

Post by Terretta » Sun, Sep 26, 2021, 2:44 PM UTC

jensneuse wrote: post #34

gonzo41 wrote: post #32

Earlier quoted context omitted.

I would place a bet along with you on that one. The question the graphql folk need to think about is who's paying for the value add of large one hit requests. cycles add up! There's a price to pay for having your api also have to parse and understand a request beyond just fetching the result.

I'd like to bet against you two. ;) I think GraphQL + a REST (JSON RPC) interface will be an optimal balance between developer experience, performance and security. I'm the founder of WunderGraph and we're doing exactly that: https://wundergraph.com/docs/overview/features/json_rpc

I like this approach, a lot.

I strongly believe developers should spend extra labor to ensure users and runtimes don’t waste cycles. I also believe labor or toil that repeats and can be automated, should. This marries both those ideas.

Finally, while thankfully you don’t say “we take security seriously” on your home page (buzzy but in practice usually a security red flag), your docs and baked-in approach show you genuinely do.

Pinged you via the TypeForm.

Re: Lessons learned from running GraphQL

#62

Post by nesarkvechnep » Sun, Sep 26, 2021, 5:54 PM UTC

timsuchanek wrote: post #58

nesarkvechnep wrote: post #30

Earlier quoted context omitted.

I bet REST API + HTTP caching is going to outperform the GraphQL APIs. And maybe most importantly, it’s going to be cheaper.

You’ll still very likely end up with dozens of http REST calls that could be one GraphQL query, hence one http call. Bias alert (I’m the founder), but I believe you should have a look at GraphQL edge caching: https://graphcdn.io

Most probably a non-issue with HTTP2.

Re: Lessons learned from running GraphQL

#63

Post by tusharmath » Mon, Sep 27, 2021, 2:59 PM UTC

tusharmath wrote: post #56

At Dream11 we love GraphQL :) It has made the lives of both — service owners and clients (Android, iOS, Web) much easier! Over the years we had packed the server with almost all the graphQL optimizations we could find on the internet. The blog outlines some of the key optimizations we had put in to improve the performance of our application code (Which doesn't have a lot to do with GraphQL, as most people have alread…

https://twitter.com/Dream11Engg?s=09

This is the new link. Some how the old link doesn't work if you have the app installed.

Re: Lessons learned from running GraphQL

#64

Post by nivertech » Mon, Sep 27, 2021, 5:33 PM UTC

I've loadtested Absinthe on a single, but beefy EC2 instance, I've got ~ 10K/s dummy GraphQL queries (not involving database, just a resolver returning the value directly).