So I get that they call it "architecture-less" because it doesn't choose between "shared nothing" and "shared disk" architectures and thus can pivot from OLTP t

So I get that they call it "architecture-less" because it doesn't choose between "shared nothing" and "shared disk" architectures and thus can pivot from OLTP to OLAP. But I have a different OLTP vs OLAP "architecture" question.... is it row-based or columnar? Is it "architectureless" in that regard also? Are they going to store data persisted both ways so you get the worst of both worlds performance-wise or is there still an OLAP vs OLTP architecture choice there? I suspect there are still some architectural choices here!