Is graphQL generally worse at performance than REST?

• gqlgen

  43 9,613 9.3 Go

  go generate based graphql server library

  

We also don’t use Node anymore. We found Node in general to be incredibly slow, not to mention single threaded. Admittedly, we did use Node (Apollo) though up until about two years ago. Now, depending on use-case, we will use Go (https://github.com/99designs/gqlgen) or Rust (https://github.com/graphql-rust/juniper). Both outperform a Node gateway but significant margins.

• juniper

  11 5,533 8.8 Rust

  GraphQL server library for Rust

  

We also don’t use Node anymore. We found Node in general to be incredibly slow, not to mention single threaded. Admittedly, we did use Node (Apollo) though up until about two years ago. Now, depending on use-case, we will use Go (https://github.com/99designs/gqlgen) or Rust (https://github.com/graphql-rust/juniper). Both outperform a Node gateway but significant margins.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

Suggest a related project