the Slashdot effect
loreweb devops culture
The crash of a small website under the traffic of a sudden front-page link, named for the site that did it nightly.
In the late 1990s a link from the tech-news community Slashdot could deliver more visitors in an hour than a hobby server saw in a year, and 'slashdotted' became the verb for the resulting outage. Successors renamed it the Reddit hug of death, but the physics never changed: legitimate flash crowds are indistinguishable, at the server, from a denial of service. CDNs and static-first architectures are the industry's long answer to it.
The Slashdot effect named what happened when a large aggregator linked to a small site: traffic arrived in minutes rather than building, and the server fell over. The pattern predates the name and has outlived the site that gave it, appearing now as a hug of death from any sufficiently large audience.
The mechanism is worth understanding precisely because it is not a gradual load problem. Normal capacity planning assumes traffic grows with some warning; a front-page link produces a step function, and systems that would handle the same volume spread over a day fail at it delivered in ten minutes. Connection limits, database connection pools and per-request memory are usually what break first, well before bandwidth.
The defences are all forms of decoupling. Static generation means a page is a file rather than a computation, caching at the edge means most requests never reach the origin, and rate limiting degrades gracefully rather than collapsing. That is one reason static site generation returned to fashion: the failure mode it eliminates is precisely the one that arrives without warning, and a file served from a CDN does not care how many people want it.
Also known as: hug of death, slashdotted