Hacker News Reader

This is a scaling question. Clearly the question is, assuming the current set up is no longer enough, what would be the best way to scale this architecture.

View on HN

Probably the easiest would be to use memcache for some of the repeated queries, specifically the items that are relatively static, such as the original post or posted item details.

It probably wouldn't help too much on the front page, since that'll update constantly and therefore just be a waste of overhead.

This doesn't really address the issue that there's no centralized information repository. With the content entirely in RAM, to distribute the app to two boxes would require either some sort of message broadcasting system, or re-architecting the data to be stored in some other way.

Reply on news.ycombinator.com