VRETA

GraphQL

GraphQL
About:Query language and runtime letting clients request exactly the data fields they need.
Problem

Every team invented its own way to stop an expensive query before it hurts us

One service counts fields, another counts nesting depth, and a third does nothing at all and just hopes. None of the approaches agree on what expensive even means, so a query that is fine on one service times out on another. Comparing notes across teams revealed we are solving the same problem three separate ways.
AAI Discovery1mo ago
1 person
Only GraphQL residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.