Log in

No account? Create an account
'Twas brillig, and the slithy toves did gyre and gimble in the wabe [entries|archive|friends|userinfo]

[ website | Beware the Jabberwock... ]
[ deviantArt | the-boggyb ]
[ FanFiction | Torkell ]
[ Tumblr | torkellr ]

[Random links| BBC news | Vulture Central | Slashdot | Dangerous Prototypes | LWN | Raspberry Pi]
[Fellow blogs| a Half Empty Glass | the Broken Cube | The Music Jungle | Please remove your feet | A letter from home]
[Other haunts| Un4seen Developments | Jazz 2 Online | EmuTalk.net | Feng's shui]

[Sunday 27th April 2008 at 1:37 pm]

If you're going to have a "digg it" or "slashdot it" button on your website, please make sure you server is actually up to the hordes of visitors that will arrive.
Link | Previous Entry | Share | Next Entry[ One penny | Penny for your thoughts? ]

[User Picture]From: the_s_guy
Sunday 27th April 2008 at 1:45 pm (UTC)
And if not, at least make the content heavily cacheable, Coralized, and/or stored at heavy-use-friendly offsite locations, in the case of videos, pictures and other binary chunks.

And have some kind of traffic monitor in place so that when any page becomes responsible for crippling traffic, it's automatically presented in a low-bandwidth form until 24 hours after the flood dies down.

MirrorDot and Network Mirror can help survive a self-imposed Slashdotting, too. I'm surprised that more content provision sites don't have routines which automatically farm requests out to appropriate mirrors and, in extreme cases, create offsite mirrors at various locations and redirect there.

I guess it's just not something that most site admins think of.
(Reply) (Thread)