4 ms·
S3 based on 100k members uploading on average 5x5MB audio files each, and a growth (new uploads) of around 10%/month: Storage: 1500GB Transfer in: 150GB
by ashleyw 18y ago
S3 based on 100k members uploading on average 5x5MB audio files each, and a growth (new uploads) of around 10%/month:
Storage: 1500GB
Transfer in: 150GB
Transfer out: 30000GB
PUT requests: 50000
GET requests: 10000000
———————————————
Total cost: $4,560.10
Not too bad if you ask me! (btw its late and I'm tired, so sorry if my figures are WAY off! :P)
- aupajo 18y agoShouldn't that be POST? PUT would be for updating the file that was originally POSTed.
- tlrobinson 18y agoNo, POST is typically for submitting data to some other "resource" for processing, while PUT is for storing data to a specific URL. HTTP/1.1 RFC: "The fundamental difference between the POST and PUT requests is reflected in the different meaning of the Request-URI. The URI in a POST request identifies the resource that will handle the enclosed entity. That resource might be a data-accepting process, a gateway to some other protocol, or a separate entity that accepts annotations. In contrast, the URI in a PUT request identifies the entity enclosed with the request -- the user agent knows what URI is intended and the server MUST NOT attempt to apply the request to some other resource." And from S3 documentation: "Objects are stored using the HTTP PUT method." S3 and similar file storage services map particularly well to GET, PUT, and DELETE.
- listic 18y agoCan this kind of bandwith be had cheaper? And by the way how did you get that 30000GB figure? It's roughly the full capacity of 100 Mbps connection.