Concept discussed in the talk: because GraphQL is highly expressive, clients can issue deeply nested queries (and even circular patterns like user→posts→author→posts). The syntactic size of a query gives no hint of its cost, making such queries a frequent performance bottleneck that requires guardrails like max_depth and execution timeouts.