TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Announcing GraphQL Rate Limiting: Protect Your GraphQL API from Bots and Hackers

5 pointsby mxstbrover 2 years ago

1 comment

ewitternover 2 years ago
Cool stuff, congrats on the launch!<p>I am excited to learn about the details for complexity-based rate limits, as there are quite a few design considerations involved. For example, how to configure which (numeric) arguments in a GraphQL query actually impact complexity. The example in the blogpost relies on `first`, which seems to be derived from Relay Connections. But implementations might differ and user other arguments.<p>We did research in this area (cf. <a href="https:&#x2F;&#x2F;arxiv.org&#x2F;pdf&#x2F;2009.05632.pdf" rel="nofollow">https:&#x2F;&#x2F;arxiv.org&#x2F;pdf&#x2F;2009.05632.pdf</a>) and proposed a specification to embed required configuration in the GraphQL schema (cf. <a href="https:&#x2F;&#x2F;ibm.github.io&#x2F;graphql-specs&#x2F;cost-spec.html" rel="nofollow">https:&#x2F;&#x2F;ibm.github.io&#x2F;graphql-specs&#x2F;cost-spec.html</a>).