Skip to content

Query resource limits #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Query resource limits #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions proposals/ResourceLimits.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
question: "How do I prevent a query from consuming too many resources?"
draft: true
---

A generalization of [ProtectionFromDeepNestedQueriesAttacks](https://github.com/graphql/faq/blob/master/proposals/ProtectionFromDeepNestedQueriesAttacks.md).
Answer is something along the lines:
* Use persisted operations if you can get away with it
* Query complexity limits
* Query depth limits
* Input document size limits
* Input variable size limits
* Timeouts as a last resort