How a Hacker News surge crashed Peakd.io and prompted a full infrastructure rebuild
A few weeks ago, Peakd.io — a community product-ranking site built by a solo developer — went down within 60 seconds of being posted to Hacker News, overwhelmed by around 500 concurrent connections. The failure stemmed from a single Express instance with no caching, a PostgreSQL connection pool capped at 20, and sequential database queries that caused cascading timeouts. The developer rebuilt the infrastructure, adding Varnish HTTP caching, PgBouncer connection pooling, Redis with write-invalidation, parallelized queries, and multiple clustered backend and frontend instances. The revamped setup now handles 200 concurrent origin requests at an average of 41ms with zero errors on a warm cache, all running on a single $24-per-month Lightsail instance. The site currently has 661 users and faces a cold-start challenge, as many product categories lack sufficient votes to generate reliable rankings.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in