The SlashDot Aftermath & RackSpace

5 thoughts on “The SlashDot Aftermath & RackSpace”

  1. What you need is a caching reverse proxy sitting between your server(s?) and the net. (Hello Squid?, see:

    Secondly, even Slashdot is not foolish enough (that’s directed at the knuckleheads that produce this blogging software) to run a straight dynamic website.

    Use a database to store your media assets, ie stories, images, etc. but your backend should be batch oriented and when updated it spits out a new batch of flat files.

    Keep up the good work, and Lord knows the slashdoters are sure to visit again.

This site uses Akismet to reduce spam. Learn how your comment data is processed.