Jason Richey wrote:
Why not just serve the images from images.wikipedia.org (which I imagine would resolve to the database machine for the moment). Am I missing some key point that makes something fancier necessary?
My inherent love for complexity? ;-)
Hmmm, well, let me think. A fancy-enough reverse proxying system could cache images on the frontend machine so that we only have to bother the database machine for write and occassional reads, whereas serving all the images directly from the db machine is going to be a fair amount of traffic.
On the other hand, since images are always going to be different from article data in some important ways, then *whatever* we do, a switch to images.wikipedia.org is probably a very good idea.
--Jimbo