图片托管网站的架构 [英] Architecture of an image hosting site

问题描述

我敢肯定，很多在这里都知道图片托管网站，像imgur，min.us中，Photobucket等。

I'm sure many here are aware of image hosting sites, like imgur, min.us, photobucket etc.

这并不是说我想开发一个，但除了刚才上传的文件，在某些目录组织它的地方，都参与了这些网站的建筑是什么考虑？特别是当有几百万页的浏览量每天（像imgur，我想像）

Not that I want to develop one, but besides just uploading the file, organising it in some directory somewhere, what architectural considerations are involved in these sites? Especially when there's millions of page views a day (like imgur, I'd imagine)

我很好奇这一点，因为它似乎很多网站（比如交友网站等）将是pretty图像密集。即使不是数以百万计的页面浏览量，什么是有效的图像交付的一些基本架构要求在线？

I'm curious about this because it seems that a lot of sites (say, dating websites etc) would be pretty image intensive. Even if it's not for millions of page views, what are some basic architectural requirements of efficient image deliveries online?

推荐答案

如果这是造成图像视图你担心，我想你会希望在一系列的服务器映像分配负载。这是一个内容分发网络的问题。第一个解决方案就是有许多服务器在一个位置，这样你小号$ P $垫的负载，下一级的解决办法是有一个范围的地理分布的服务器，并根据客户端的IP地址，引导他们来个亲密服务器

If it's the load caused by image views you're worried about I suppose you would want to distribute the images across a range of servers. It's a content delivery network problem. First solution is just to have lots of servers in one location so that you spread the load, next level solution is to have a range of geographically distributed servers and depending on the IP address of the client direct them to a close server.

我不知道真的是有需要的服务器的地理分布只服务图像，图像服真的是相当低负荷。但是，如果你开始投放视频这肯定会适用。

I'm not sure there is really a need for a geographic distribution of servers just to serve images as image serving is really quite low load. But this would certainly apply if you started to serve video.

这篇关于图片托管网站的架构的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！