Web Development
Bug Report
One nested GraphQL query pinned our API at 100% CPU: depth limits, cost analysis and introspection
A single GraphQL request with deeply nested author, posts and comments fields took 40 seconds and saturated every API pod, because the schema allowed unlimited depth and list sizes. The defensive controls we added: depth and complexity limits, page caps, persisted queries and an introspection policy.