使用Amazon Web Services S3和Google Application Engine的存储的相对优势 [英] Relative advantages of storage using Amazon Web Services S3 vs Google Application Engine

问题描述

您认为Amazon Web Services S3与Google Application Engine相比的优点和缺点是什么？在我问的时候，两者的每GB成本大致相似;我没有看到任何关于服务质量的广泛投诉;所以我认为决定哪一个使用可能取决于API（所有的东西）。

What do you see as the advantages and disadvantages of Amazon Web Services S3 compared with Google Application Engine? The cost per gigabyte for the two is, at the time I ask, roughly similar; I have not seen any widespread complaints about the quality of service; so I think the decision of which one to use may depend on the API (of all things).

Google的API将你的内容打破他们所谓的静态内容，例如CSS文件，网页图标，图片等，以及非静态动态生成的HTTP响应。对静态内容的请求将提供给请求它的用户，直到达到带宽限制为止;非静态请求将被满足，直到达到您的带宽或CPU限制。对于您的非静态请求，您可以提供您能够在Python中表达的任何逻辑，因此您可以选择服务的人。

Google's API breaks your content into what they call static content, such as your CSS files, favicons, images, etc and non-static dynamically-generated HTTP responses. Requests for static stuff will be served to whoever requests it until your bandwidth limit is reached; non-static requests will be fulfilled until your bandwidth or CPU limit is reached. With respect to your non-static requests, you can provide any logic you are able to express in Python, so you can be choosy about who you serve.

Amazon的API所有您的内容作为桶中的Blob，并提供访问协议，让您区分各种可实现的请求，从世界可读到所有者。如果你想要的东西，不是在工具包，虽然，我不知道你做什么，除了思考分发你的URIs。

Amazon's API treats all your content as blobs in a bucket, and provides an access protocol that lets you distinguish between a variety of fulfillable requests ranging from world-readable to owner-only. If you want to something that's not in the kit, though, I don't know what you do beyond being thoughtful about distributing your URIs.

你看到之间的差异他们俩？有你喜欢的其他云存储服务吗？ Zetta 今天发布了新闻稿，但他们正在测试版应用程序中搜索至少10 TB，我的客户都没有（还）;和 Joyent 在不久的将来可能会做某事。

What differences do you see between the two? Are there other cloud storage services you like? Zetta had a press release today, but they're looking for a minimum of ten terabytes on the beta application, and none of my clients are there (yet); and Joyent will probably do something in the near future.

推荐答案

GAE对通过appcfg.py上传的静态文件的每个限制为10 MB（请查看 http://code.google.com/appengine/docs/python/tools/uploadinganapp.html ）。很明显，你可以编写代码将大文件分割成多个位，并在下载时重新组装，但它建议Google不要求App Engine只是作为一个简单的CDN使用，如果你想使用它作为一个必须做一些工作。 S3会做任务开箱即用，你所要做的就是抓住第三方界面应用程序。

GAE has a limit of 10MB each on static files uploaded through appcfg.py (look right at the bottom of http://code.google.com/appengine/docs/python/tools/uploadinganapp.html). Obviously you can write code to slice large files into bits and reassemble at download time, but it suggests to me that Google doesn't expect App Engine to be used just as a simple CDN, and that if you want to use it as one you'll have to do some work. S3 does the job out of the box, all you have to do is grab a third-party interface app.

如果你想做一些非标准的文件访问在S3上，然后大概亚马逊希望你春天在EC2上的服务器实例。一旦这样做，你比GAE的环境有更多的灵活性，但你支付更多（现金，可能在维护）。

If you want to do something non-standard with file access on S3, then probably Amazon expects you to spring for a server instance on EC2. Once this is done, you have much more flexibility than GAE's environment, but you pay more (in cash and probably in maintenance).

GAE的加分是对于小型应用程序（高达1GB存储空间，1GB带宽和每天130万次点击都是免费的）提供便宜功能： http://code.google.com/appengine/docs/quotas.html ）。根据您的使用，这可能是重要的，或者它可能与您的总带宽成本的规模不相关。

The plus point for GAE is that it has "cheap" on its side for small apps (up to 1GB storage, 1GB bandwidth and 1.3 million hits a day are free: http://code.google.com/appengine/docs/quotas.html). Depending on your use, this might be significant, or it might be irrelevant on the scale of your total bandwidth costs.

巧合的是，我刚才这几天看在GAE第一次。我拿了一个旧的Perl CGI脚本，并把它变成一个GAE应用程序，它是启动和运行。总共大约10小时，包括阅读GAE介绍文档和记住Python应该如何工作足以写几百行。我猜测，这是更多的努力，比加载一组文件到S3，但比维护EC2服务器更少的努力。但是，我没有使用亚马逊。

Coincidentally, I have just this last couple of days looked at GAE for the first time. I took an old Perl CGI script and turned it into a GAE app, which is up and running. About 10 hours total, including reading the GAE introductory docs and remembering how Python is supposed to work enough to write a couple of hundred lines. I'd speculate that's more effort than loading a bunch of files onto S3, but less effort than maintaining EC2 server(s). However, I haven't used Amazon.

*除了Google刚刚向我提供了GAE Java支持的预览。

* Except that Google has just offered me a preview of GAE's Java support.

**注意到您可以设置chron作业，但它们受到与任何其他请求相同的规则（30秒运行时，不能修改文件等）。

** Just noticed that you can set up chron jobs, but they're limited by the same rules as any other request (30 second runtime, can't modify files, etc).

这篇关于使用Amazon Web Services S3和Google Application Engine的存储的相对优势的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！