Storage Tiering Service  ·  View 27 of 31  ·  6 · Operations

Roadmap

Prove that nothing is lost, then earn the saving on large objects, then go after small objects, tape and a second custodian.

Editable source SVG draw.io All views
Proof · 10 weeks Resolver at 1.4 M/s p99 measured Movement under chaos kill · drop commits Shadow on real logs projected saving MVP · to month 6 Catalogue on every read Hot · warm · cold objects ≥ 1 MB Declarative policy break-even · rings Holds · budgets · drift Phase 2 · months 6–12 Packs + compaction cohorts under 1 MB Tape archive EOS + CTA Bulk recall · staging Predictive, in shadow Phase 3 · months 12–24 Offsite vault custodian Recall price quotes Tenant cost reporting Region as a dimension Roadmap — Never Lose an Object, Then Save Money, Then Go Deeper Application we own Decision point Security / platform The MVP leaves objects under 1 MB where they are. That forgoes about 7% of the target saving and avoids 75% of the movement requests. v 1.0 · owner Storage Platform Architecture · date 2026-09

Sequencing decisions

  • The proof phase is about safety and the read path, not savings: the resolver at full load, and copy-verify-commit-release under deliberate worker kills, dropped commits and a site loss.
  • The MVP tiers only objects of 1 MB and above. Packing is Phase 2, as the requirement sets it, and the correct placement for a small object until then is wherever it already is.
  • The predictive classifier enters in shadow in Phase 2 and must beat the declarative policy on realised, not projected, break-even for two consecutive cycles before it moves anything.

Numbers

  • Proof 10 weeks, MVP by month 6, Phase 2 by month 12, Phase 3 by month 24. Objects under 1 MB are about 75% of objects and about 4% of bytes.

Exit criteria for the proof

  • Resolver p99 under 8 ms at 1.4 M/s with a 4× burst; zero lost objects across 10 million chaos movements; shadow projection of at least 40% net saving on real access logs.