最流行的媒体丰富网站如何实施他们的媒体库？
我想知道那些流行的媒体丰富网站如何实现他们的媒体库。他们是否将所有媒体文件存储在数据库中？他们使用什么样的数据库？他们是否采用其他机制来提高性能？
感谢您的任何回复。
I'm wondering how those popular media rich websites implement their media library. Do they store all the media files in the database? What kind of database do they use? Do they employ other mechanism to boost the performance?
Thanks for any response.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
“流行媒体网站”的范围相当广泛，但通常高容量的富媒体网站使用内容交付网络 ，例如 Akamai 等或基于云的存储，例如 AmazonS3
"Popular Media Sites" is pretty broad, but typically high volume rich media sites use Content Delivery Networks, such as Akamai, etc or cloud based storage like AmazonS3
你问的是一个很难回答的问题。
作为介绍性读物，我建议您查看高可扩展性的 Youtube 架构 。 YouTube 是一个很好的现实生活例子，展示了以媒体为中心的网站如何运作。
令人惊讶的是，提供实际的媒体文件并不是瓶颈。更困难的部分是同步所有媒体元数据、生成缩略图等。媒体文件始终可以从集群托管，如果是非常受欢迎的视频，也可以从 CDN 托管。
阅读链接以获取更深入的信息。
You are asking a very difficult question to answer.
I recommend that as an introductory read you check out Youtube Architecture on High Scalability. Youtube is a very good real-life example of how a media-centric website works.
Surprising as it may be, serving the actual media files is not the bottleneck. The harder part is getting all the media meta-data synched, generating thumbnails, etc. Media files can always be hosted from a cluster, or from a CDN in case of an extremely popular video.
Read the link for more in-depth info.
作为流行媒体网站的开发人员，我们将视频服务卸载给第三方（YouTube 和 BrightCove）。然后，我们根据情况在自定义播放器中托管该视频，以分层添加广告和其他功能。抽空视频流最好由在其架构中投入大量精力和金钱的其他人来处理。
与所有事情一样，您需要决定您的需求是否足够具体以保证内部开发还是与其他工具集成的努力。
Speaking as a dev on a popular media website, we offload the serving of video to 3rd parties (YouTube and BrightCove). Depending on the situation, we then host this video within a custom player to layer in ads and other features. Pumping down video streams is best handled by someone else who has invested a lot of energy and money into their architecture.
As with everything, you need to decide if you needs are specific enough to warrant developing in-house vs effort of integrating with other tools.