key-value-ssd · limited · also KV-SSD, NVMe key value drive

Key-value SSD

A key-value SSD stores and retrieves variable-length values by key, through commands such as Store, Retrieve, Delete, Exist and List, instead of fixed-size logical blocks.

The NVMe Key Value Command Set (Revision 1.1, 2024) limits keys to 16 bytes and aborts longer ones with Invalid Field in Command, while a value may run from zero bytes to a maximum set by the namespace's KV format. A namespace can offer up to 16 KV formats, the command set is Command Set Identifier 01h, and Store, Retrieve, Delete, Exist and List are mandatory. [2]

Store and Delete are atomic for a single pair, there are no fused operations and no ordering guarantee between concurrent commands on one key, and List order is unspecified but stable while contents do not change. Namespace size and utilisation are counted in bytes, each pair needing at least key plus value size, and compression is out of scope. [2]

The SNIA Key Value Storage API (version 1.1, 2020) is the host-side counterpart, with at most one Key Space per NVMe namespace or SCSI logical unit, optional Key Groups and device-reported key and value limits. [3]

Relations

related
NVMe, Computational storage drive, Block storage, Object storage

Advantages

  • Applications can address data by key without first mapping it to logical blocks, and can query stored keys on the device itself. [2, 3]

Limitations

  • Longer application keys must be shortened or mapped by the host. [2]
  • Multi-key transactions and ordered range scans have to be built by the host. [2]

Citations

  1. NVM Express Key Value Command Set Specification, Revision 1.1, ratified 5 August 2024. (accessed 2026-10-16)
  2. SNIA Key Value Storage API Specification, Version 1.1, 28 September 2020. (accessed 2026-10-16)

Further reading

  1. Key-value SSD (accessed 2026-03-26)
Sources & caveats
  • Both documents define interface semantics only, and neither names implementing products or describes adoption.
  • Neither gives performance, capacity, endurance or cost figures, so no advantage over block SSDs is quantified; the numbers are specification limits.

JSON: /data/terms/key-value-ssd.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Key-value SSD. Hesela. 2026-10-22. https://hesela.dev/terms/key-value-ssd/