All that applies to regular kv stores abstracted through filesystems and block device layers just fine.
But when your latency requirements are so tight that you cannot possibly afford the latency penalty of a filesystem, you better have a good business case to justify either developing a custom bare-metal-nvme (which is $$$$$ and takes time) or getting a multi-TB RAM system, which is also $$$$$, but far more predictable, and can be put into production today, not 6+ months later when you finish developing your custom kv store.
For the other 99.999% of use cases, sure, just go with NVMe backing your regular virtualization/containerization infrastructure.
