4 ms·
Perhaps a naive question but why would glacier try to discourage bulk retrieval? Is it because the data is fragmented physically?
by cm2187 11y ago
Perhaps a naive question but why would glacier try to discourage bulk retrieval? Is it because the data is fragmented physically?
- syncsynchalt 11y agoWe don't actually know how glacier data is stored (though there are several theories from regular s3 to tape robots to experimental optical media).
- ufmace 11y agoI suppose part of the neat trick of it is that because we don't have to know, Amazon can switch it out for something else anytime it's convenient for them, or some new tech comes up. Or split thing up among several methods and compare costs. As long as they structure their operations such that nothing is ever lost and everything can be retrieved with a few hours notice at any time, they can try anything they want.
- cpayne 11y agoI'm sure that was a commercial decision, not a technical one. They could be running Glacier storage at cost (or even a slight loss). But they make their profit when you try to get your data out. I'm not implying anything nefarious - more along the lines that Amazon (could have!) looked at the market and compared demand to what they were offering. Then found something that scratched an itch...
- boulos 11y agoIn most of these cases, the technical decisions impact the commercial. If writing megabytes were "technically" cheaper than reading, you can either choose to pass that cost onto customers or simplify the pricing model assuming some read-to-write ratio. They didn't just set the prices (or the pricing model) to amuse themselves. Disclaimer: I work on Compute Engine.
- melted 11y agoBecause they power down cold racks. It's called Glacier for a reason.