3 ms·

>I guarantee you they would have recouped the costs Do you know the costs. Please share

ClumsyPilot 4y ago
For a static version? I am willing to bet a single server with 10 Gb connection can do it
skilled 4y ago
The very basic math on this is: 1,560,000 pages x 150 KB/page = 234 GB 234 GB x $0.023 per GB = $5.38 this is just to host all the pages themselves. Data transfer per month: (Assuming 10 million pageviews) 10,000,000 x 150 KB = 1,500 GB 1,500 GB x $0.09 per GB = $135 GET and all other Requests: $0.0004 per 1,000 requests 30,000,000 / 1,000 x $0.0004 = $12 --- Storage cost: $5.38 Data transfer cost: $135 Requests cost: $12 Total estimated cost per month: $5.38 + $135 + $12 = $152.38 --- This is NOT considering images themselves, though you get a general idea of what I am implying. Enjoy the math. I was happy to share it with you.
- sklargh 4y ago
  One of the more useful comments I've read in weeks. Thanks.
- c2h5oh 4y ago
  Or $3.36 if your put it on Cloudflare R2 (s3 compatible) and host it there
  - renewiltord 4y ago
    Okay, well, in that case I will put down $500 to pay for that for ten years or whatever and one of you guys can wget -r it and put it on Cloudflare R2. Reply to this post once you have set up the Cloudflare account and posted the content on it and I'll send you an email you can give me admin credentials on so I can put billing details in.
    - c2h5oh 4y ago
      It's rate limited. A distributed effort to create a complete backup will be starting soon https://wiki.archiveteam.org/index.php/DPReview https://wiki.archiveteam.org/index.php/DPReview
- echelon 4y ago
  Very affordable to keep online as an archive or infrequently updated blog. If the founder really wanted it back, the correct response would have been asking Amazon in a public forum if they would like to pass on ownership. If done in a gracious and respectful tone, I have no doubt that would have engendered all around good feels. It could have even compelled Amazon to put one half quarter of engineering headcount into wrapping the site up in an AWS account to hand over. The founder should have said they'd be happy to take on costs and future burden, host it on AWS, and continue to link to Amazon products and storefront. Should have said that they were grateful for Amazon's stewardship and that they'd like to continue carrying the torch. An easy all-around win. The actual response from the founder was too negative and blame ridden if their intention was to resume operation.

For a static version? I am willing to bet a single server with 10 Gb connection can do it

The very basic math on this is: 1,560,000 pages x 150 KB/page = 234 GB 234 GB x $0.023 per GB = $5.38 this is just to host all the pages themselves. Data transfer per month: (Assuming 10 million pageviews) 10,000,000 x 150 KB = 1,500 GB 1,500 GB x $0.09 per GB = $135 GET and all other Requests: $0.0004 per 1,000 requests 30,000,000 / 1,000 x $0.0004 = $12 --- Storage cost: $5.38 Data transfer cost: $135 Requests cost: $12 Total estimated cost per month: $5.38 + $135 + $12 = $152.38 --- This is NOT considering images themselves, though you get a general idea of what I am implying. Enjoy the math. I was happy to share it with you.

sklargh 4y ago
One of the more useful comments I've read in weeks. Thanks.
c2h5oh 4y ago
Or $3.36 if your put it on Cloudflare R2 (s3 compatible) and host it there
- renewiltord 4y ago
  Okay, well, in that case I will put down $500 to pay for that for ten years or whatever and one of you guys can wget -r it and put it on Cloudflare R2. Reply to this post once you have set up the Cloudflare account and posted the content on it and I'll send you an email you can give me admin credentials on so I can put billing details in.
  - c2h5oh 4y ago
    It's rate limited. A distributed effort to create a complete backup will be starting soon https://wiki.archiveteam.org/index.php/DPReview https://wiki.archiveteam.org/index.php/DPReview
echelon 4y ago
Very affordable to keep online as an archive or infrequently updated blog. If the founder really wanted it back, the correct response would have been asking Amazon in a public forum if they would like to pass on ownership. If done in a gracious and respectful tone, I have no doubt that would have engendered all around good feels. It could have even compelled Amazon to put one half quarter of engineering headcount into wrapping the site up in an AWS account to hand over. The founder should have said they'd be happy to take on costs and future burden, host it on AWS, and continue to link to Amazon products and storefront. Should have said that they were grateful for Amazon's stewardship and that they'd like to continue carrying the torch. An easy all-around win. The actual response from the founder was too negative and blame ridden if their intention was to resume operation.