Menu

Post image 1
Post image 2
1 / 2
0

Postmortem: GraphQL 16 N+1 Problem Caused 3-Second Page Loads for 1 Hour

DEV Community·ANKUSH CHOUDHARY JOHAL·about 1 month ago
#VRG4OLul
Reading 0:00
15s threshold

At 14:17 UTC on March 12, 2024, our production dashboard alerted on a p99 page load time of 3.2 seconds for our product catalog, up from a baseline of 110ms. The root cause? A silent regression in GraphQL 16’s default resolver behavior that triggered a catastrophic N+1 query storm affecting 12,000 active users for 47 minutes. 🔴 Live Ecosystem Stats ⭐ graphql/graphql-js — 20,313 stars, 2,046 forks 📦 graphql — 147,625,385 downloads last month Data pulled live from GitHub and npm. 📡 Hacker News Top Stories Right Now AI uses less water than the public thinks (101 points) Ask HN: Who is hiring?…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More