Menu

Autopsy #13: The useEffect Dependency Loop That DDoSed Our Own API
πŸ“°

Autopsy #13: The useEffect Dependency Loop That DDoSed Our Own API

DEV Community: frontendΒ·frontend.rocksΒ·about 9 hours ago
#EOS24Cp1
#devtofrontend#devto#dev#status#filter
Reading 0:00
15s threshold

Incident Report

API gateway telemetry recorded a 48x spike in GET /api/items traffic and a 64% rate of 429 Too Many Requests responses three minutes after deploying a filter bar refactor. Client error tracking simultaneously logged Maximum update depth exceeded across 19% of active dashboard sessions.

Network waterfall : A single filter click spawned 47 uncancelled GET /api/items?status=open requests within 420 ms before the edge rate limiter tripped.

CPU profile : Main-thread scripting saturated at 99% CPU due to continuous React commit phases and V8 minor garbage collection pauses.

Failed naive patch : Adding a 300 ms debounce around the fetch call.

Debouncing only delayed the first burst by 300 ms.…

Continue reading β€” create a free account

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