You can also combine these two: if you have a numeric id that increases by 1 every row, you can delta-encode that to just get a massive list of 1's, which you can then run-length encode to just be "the delta for the next million rows is 1", saving huge amounts of space.
You generally don't do this with AOS/SOA, because you do want to be able to random-access your entries ("index" them, in database terms) and I/O performance is much less important. Databases have this issue too, which is why indexes tend to either not be available or much slower in column-oriented DBs.
EDIT: ah, read the original commenter a bit too quickly, missed that they mentioned run-length encoding. Apologies.
I believe Vortex is unique in its ability to retain random access while recursively compressing data. And turns out that this is helpful for both in-memory _and_ on-disk (we might write about that in the future)!
I unfortunately didn't have much space to write about that in this blog, but in the compression section I did link to other blogs that we have written that go into much more detail, if you are interested :D
I call that a pretty positive tradeoff :)
Array of Structures vs Structure of Arrays.
People who might be technical and might even intuitively understand what is meant by "Array of Structures vs Structures of Arrays" might not be familiar with the acronym AOS vs SOA, especially given SOA is already a technical acronym their brain might shortcut to, "Service Oriented Architecture", even if instantly dismissed as clearly incorrect.
By expanding the algorithm you also help let people better decide if they want to spend the time reading up more about it.
Maybe you agree with that and just disagree with where the line should be drawn?
I'd also err on the side of generally assuming that most people, even in a technical forum, don't know all acronyms unless they're very widely known outside of the topic at hand. I don't think AOS vs SOA comes anywhere close to that line.
Some acronyms are of course better understood by their acronym, I wouldn't introduce a Local Area Network (LAN), or Domain Name Resolution (DNS), so like all guidelines there's judgement to be made.
Even then, if I were writing an intro to DNS, then I would call it an Introduction to Domain Name Resolution (DNS), because it is specifically targeted as an introduction. I wouldn't do the same for SQL, because no-one calls it Structured Query Language. Fairly often it would be more confusing if they did expand it, because quite often when people talk about SQL they're not really talking about the language at all, but using it as a short-hand for talking about SQL-compatible databases, or more specifically talking about relational database management systems (RDBMS), but "SQL" is a useful shorthand to contrast to "No-SQL" databases that were popularised a decade or two ago.