News for hackers. Stuff that matters.

A comment on Amazon S3 Pricing Changes Effective April 1, 2014. Parent comment

Re:Amazon S3 Pricing Changes Effective April 1, 2014 by hrrsn on Thursday March 27, 2014 @03:53AM (#7479112)
Why wouldn't they put all of that in a Backblaze Storage Pod? 2 months of AWS costs could've built more than 2 pods and stored everything with plenty of space to spare.
[ Parent | on HN ]
Re:Amazon S3 Pricing Changes Effective April 1, 2014 by tiquorsj on Thursday March 27, 2014 @05:23AM (#7479323)
Price out the backup solution for that back blaze. Then make the backblaze geograohiclly redundant. Then write the system to keep them in sync. Then add versioning. Then pay for someone to manage it. Now you are getting towards the real cost of that backblaze to replace S3.
[ Parent | on HN ]
Re:Amazon S3 Pricing Changes Effective April 1, 2014 by herokusaki on Thursday March 27, 2014 @07:53AM (#7479754)
>Then write the system to keep them in sync. Then add versioning.

Are there any ready-to-deploy solutions for this?

[ Parent | on HN ]