How We DDoS Ourselves with SSR
summary
Product Hunt admits that SSR setup repeatedly overwhelms its stack for about a year: Rails on Heroku spawns a Node process with pre-rendered true, those Node calls serialize into a chain, and pages block while JavaScript rendering runs. A switch to an Nginx front with a separate Heroku Node-in-Rails proxy and then a move to JSON/GraphQL API endpoints reduces cross-process blocking. Final fix is migration to AWS EC2 autoscaling and splitting Node and Rails into clusters, which measurably stops the self-inflicted DDoS.
AI-written summary · about
related talks
43mStack Smashing
37m5 Years of Rails Scaling to 80k RPS
39mBuilding a highly scalable exchange - To react or not to react
52mNot all attacks are malicious: DDoS from outside and within
40mHow Shopify Scales Rails
40mZero-downtime payment platforms
44mIntroduction to application scaling
27mSSR & SSG in NextJS