|
Right, the pricing model for AWS Glacier definitely gets you when you do retrievals. Nearline looks a million times better in this regard.
Also, I'm thinking that access to the data would be mediated by a service layer. The service could make informed decisions (based on recent access) about which objects to keep in online vs nearline storage. It maybe as simple as keep everything in nearline.
On access move to online and keep for the next n days.
Notice the retrieval throughput scales with the amount of data you have in storage. 4 MB/s per TB of storage. So at PB-scale this is looking pretty good.
-john From: owner-discuss@xxxxxxxxxxxxxxxxxxxxxxx <owner-discuss@xxxxxxxxxxxxxxxxxxxxxxx> on behalf of Matthew Turk <matthewturk@xxxxxxxxx>
Sent: Thursday, March 12, 2015 1:38 PM To: discuss@xxxxxxxxxxxxxxxxxxxxxxx Subject: Re: Google "Nearline" service Hi Johns Towns and Readey,
JR: This is a pretty promising service! The discussion on hacker news was pretty interesting as well.
JT: The cost for retrieval is pretty low, and they obliquely compare quite favorably it to Glacier. Supposedly very, very fast retrieval speeds too.
-Matt
On Thu, Mar 12, 2015 at 11:44 AM, John Towns - NCSA Cog
<jtowns@xxxxxxxxxxxxxxxxx> wrote:
|