Architecture

NVMe-backed Object Tier

An architecture placing NVMe flash as a high-performance local storage tier beneath the S3 API, serving hot objects with microsecond-level latency while cold objects remain on HDD or cloud storage.

7 connections 2 resources

Summary

What it is

An architecture placing NVMe flash as a high-performance local storage tier beneath the S3 API, serving hot objects with microsecond-level latency while cold objects remain on HDD or cloud storage.

Where it fits

NVMe-backed tiers eliminate the cold scan latency inherent in HDD-based object stores. By placing frequently accessed objects on NVMe, the architecture delivers flash-speed reads through the standard S3 API — bridging the gap between local SSD performance and S3 ecosystem compatibility.

Misconceptions / Traps
  • NVMe capacity is expensive per GB. The tier only works economically when a small percentage of objects are hot. Without effective tiering policies, costs escalate quickly.
  • NVMe tier management adds operational complexity. Cache eviction, promotion policies, and tier migration must be tuned for the workload's access patterns.
Key Connections
  • depends_on NVMe-oF / NVMe over TCP — the transport for disaggregated flash
  • solves Cold Scan Latency — flash-speed access for hot objects
  • scoped_to Tiered Storage, Object Storage

Definition

What it is

Using NVMe flash storage as a high-performance local tier beneath or alongside S3-compatible object storage to reduce tail latency for hot objects and time-sensitive workloads.

Why it exists

Even with separation of storage and compute, some workloads (AI inference, real-time analytics) cannot tolerate S3's HTTP-based latency. An NVMe tier provides sub-millisecond local access for hot data while S3 serves as the durable, cost-effective cold tier.

Primary use cases

AI/ML hot data tier, real-time analytics acceleration, low-latency checkpoint storage, tiered object storage.

Recent developments

Latest signals
  • S3 Express One Zone is the canonical hyperscaler NVMe-backed object tier. Single-digit-ms latency, ~10× faster vs S3 Standard, ~100 MB/s single-stream throughput — the production reference for "NVMe-backed S3" in AWS. Per AWS — S3 Express One Zone storage class and AWS Blog — Announcing S3 Express One Zone.
  • The "Postgres wants NVMe on hot path, S3 everywhere else" framing. The New Stack's 2026 framing of how modern databases see the storage hierarchy: NVMe-backed object tier for hot pages + WAL, S3 for durable bulk. NVMe-backed object storage is now a first-class architectural primitive in transactional database design. Per The New Stack — Why Postgres Wants NVMe on the Hot Path, S3 Everywhere Else.
  • AI/ML use case is the dominant driver. AWS positions Express One Zone first as the AI/ML hot tier — model artifacts, training scratch, intermediate shuffles, GPU checkpoint sync — where the single-AZ constraint isn't a problem and the latency win compounds across thousands of GPU hours. Per AWS Docs — Optimizing S3 Express One Zone performance.
  • Premium-tier economics: priced for performance, not cold capacity. Vantage's analysis underlines that Express One Zone is a premium tier — pay for hot access, not cold storage. Pairs with Intelligent-Tiering for the cold tier; don't dual-stack NVMe + Standard for the same workload. Per Vantage — Unpacking S3 Express One Zone: Balancing Low Latency with Costs.
  • NVMe-backed object tiers also produced by ICMS / CMX vendor cohort. Solidigm, VAST, DDN, Cloudian, MinIO all shipping NVMe-backed object tiers in 2026, often DPU-fronted, often as the "Tier 3.5" pattern between local SSD and cold S3. The pattern is no longer hyperscaler-exclusive. Per project notes + Hyperglance — AWS S3 Pricing Guide 2026.
  • 2026 production convention: pair NVMe object tier + Directory Bucket + AZ-co-located compute. The full performance stack: Directory Bucket namespace + NVMe-backed Express One Zone + EC2/EKS/Lambda pinned to the same AZ → LAN-scale latency end-to-end. Documented as the canonical pattern. Per AWS Docs — Best Practices to Optimize S3 Express One Zone Performance.

Connections 7

Outbound 5
scoped_to3
S3Object StorageDirectory Buckets / Hot Object Storage
depends_on1
NVMe-oF / NVMe over TCP
solves1
Cold Scan Latency
Inbound 2
enables2
NVMe-oF / NVMe over TCPZoned Namespace (ZNS) SSD

Resources 2

DocsHigh
aws.amazon.com/s3/storage-classes/express-one-zone/

AWS S3 Express One Zone as the canonical NVMe-backed object tier delivering single-digit-millisecond latency.

DocsHigh
nvmexpress.org/

NVM Express specifications and ecosystem resources for the storage protocol underlying high-performance object tiers.