Re:Lessons learned from running GraphQL
by jjtheblunt on Saturday September 25, 2021 @02:43AM
(#28651031)
I wonder if they feel like Node was worth it. (seriously)
[ Parent
| on HN ]
Re:Lessons learned from running GraphQL
by brabel on Saturday September 25, 2021 @03:53AM
(#28651352)
Exactly, the problems they found were mostly Node problems, not GraphQL problems.
Re:Lessons learned from running GraphQL
by Zababa on Saturday September 25, 2021 @08:09AM
(#28652495)
I wonder why we haven't seen yet some more optimisation for JS. The only thing I'm aware of is the Google Closure Compiler. With everyone using TypeScript, there must be a way to use all that type information to make JS run more efficiently, or compile parts of your TypeScript code.
Re:Lessons learned from running GraphQL
by nesarkvechnep on Saturday September 25, 2021 @06:34AM
(#28652016)
Seems to me Elixir + Absinthe would’ve been a better tech stack.
Re:Lessons learned from running GraphQL
by pdimitar on Saturday September 25, 2021 @07:58AM
(#28652425)
I adore Elixir and have made a good career around it. I'll love it until my grave.
But with that many servers I can't help but wonder if Rust wouldn't be a better choice. I don't think they'll even need 100 which, as OP pointed out, will drastically reduce their operational complexity.
Furthermore, the strong static typing would have avoided the megamorphic functions right from the start.
Re:Lessons learned from running GraphQL
by l-lousy on Saturday September 25, 2021 @08:04AM
(#28652464)
Yeah I agree with rust, I have some simple database fetching servers that run crypto functions as well (I.e. login) and for simpler operations they can quickly get to 100K+ requests per second on a single host