So the obvious question is how does this very knowledgeable industry, those actually in this industry, have it so wrong?
Well, they have had it “wrong” in this particular sense for a long time. Various kinds of networked storage are sold to companies as universal good solutions and while they may in fact provide cost and management savings for word processing, spreadsheets, and the like they provide significant compromises for high transaction volume database applications. That doesn’t make it a bad product if one is knowledgeable about its characteristics and uses it accordingly, but it can mean that it is a bad product for some companies for their database applications.
In some cases, these characteristics don’t matter because the volume and critical speed of transactions does not require highest performance. Or, as been found by a number of companies using the old rotating rust type of networked storage with RAID to cuts costs and a cache to reduce apparent write time, they work OK during normal processing and then are terrible when it comes to an operation like restoring a backup which swamps the cache. Pure seems likely to not have that problem and so should work for a larger number of companies.
I don’t know that this is a factor which should retard the adoption of Pure in a meaningful degree … even if the industry were to actually wake up and pay attention to these issues, i.e., stop drinking their own koolaid. I have raised the issue because Pure is claiming latency speeds which seem dubious to me unless they are measured within the box rather than from the other end of the cable. It doesn’t help that Pure is missing from sources like the SPC-1 benchmarks http://spcresults.org/ apparently because the benchmark rules do not allow some of the “tricks” which Pure uses to achieve their results. That doesn’t mean that those “tricks” don’t work in practice, but it does mean we don’t have a standardized comparison.