On top of that, the DRAM-like form is supposed to much further lower latency by 1) getting rid of NVMe and software overhead and 2) letting you read/write as little as a (64b) cache line at a time. We still don't know what the exact remaining latency is, and I bet the few with access through this program will still be NDAd from talking about it. We also don't know about the price/GB.
Those numbers, esp. price, will have a lot to do with how broad an impact this has at first: you can imagine a scenario where most folks currently building large DBs would find it worthwhile to replace 2/3 of their RAM with 5x as much of this stuff for the same price, though that seems kind of unlikely to be imminent. Or we may find out it's only going to be worth it in some niche applications and the rest of us have to wait some generations before it reaches us (if it ever does).
NVMe Flash is, obviously, still sufficient for a lot of workloads and today is nothing like, say, 2004 when I was writing DB-backed apps and HDD seeks were my bane. Notably, if your OLTP DB can have a lot of transactions in flight at once, or your reporting workload is doing sequential reads, you can take advantage of the very high throughput of modern Flash SSDs when working on lots of I/Os in parallel.
