VRETA

GraphQL

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

Our resolver graph quietly turned one request into hundreds of database calls

Nothing in the query itself looked expensive, but each nested field triggered its own lookup against the database. Nobody noticed until a dashboard page timed out under real traffic. Adding a batching layer after the fact meant touching resolvers we had not looked at in a year.
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.