From 48fe5be8a4db4d3ee84d340f0ac051b9663385ea Mon Sep 17 00:00:00 2001 From: Joel Turkel Date: Fri, 21 Jun 2019 09:40:13 -0400 Subject: [PATCH] Resource limits --- proposals/ResourceLimits.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 proposals/ResourceLimits.md diff --git a/proposals/ResourceLimits.md b/proposals/ResourceLimits.md new file mode 100644 index 0000000..2f10eda --- /dev/null +++ b/proposals/ResourceLimits.md @@ -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