3 ms·

Practically speaking, how would warm storage like that be implemented?

• dredmorbius 7y ago
  Usually tape libraries. A problem with most forms of warm storage is that they involve moving media around, which itself can lead to degradation. I would like to see some write-one and really last forever form of storage to come into widespread use. That seems ... like it's still a few years off. And you still have the issue of how such storage is read, and how that affects total lifetime.
  • ccostes 7y ago
    Sounds like what they're doing at Microsoft with Project Silica https://news.microsoft.com/innovation-stories/ignite-project-silica-superman/ https://news.microsoft.com/innovation-stories/ignite-project...
    • dredmorbius 7y ago
      That definitely is in the direction I'm considering.
• kevingadd 7y ago
  As a compromise you could have it be more about availability and rate-limiting - if you've got a given piece of data split across 4 currently-live mirrored storage disks and you've got 32 front-end machines able to serve it up to users, you're using operational capacity for that which could be used for other higher-demand data. Assuming you have a robust backup/recovery strategy, low-demand data could be stored across 2 or 3 live disks (note: you'd still want backups somewhere for emergency recovery) instead, and have a smaller number of front-end machines dedicated to providing data to users. In that case if the low-demand data front-end machines get too much load, you'd be entering a queue to be served. Not sure that's realistic here though, it sounds like the main problem is just the volume of data so whether the storage for the data is hot, warm or cold isn't necessarily going to make a big difference and having enough frontends to serve the content isn't a big problem (in comparison) either