>Interesting, the separate compute and storage tiers is another system going that direction which I think is becoming almost the standard at this point, especially for "cloud-native" things designed to run on k8s. From what I can tell (it isn't very explicit on this point) they are avoiding a distributed consensus at the storage layer and instead relying on a single writer/multiple reader model with the single writer being enforced by assignment of the tablets in the compute tier, with the tablet being responsible for writing to multiple storage nodes for durability? (But I might be wrong)

Hmmm, 4D around the 90's/early 2000's also keep the data and code separated in 2 different files. They maybe still do, but haven't touched it in a while. Tech is more and more like fashion, if you wait around long enough it will come back. ;-)