Databases & Storage · advanced
Columnar Storage
Column-oriented layout for analytics: compression and vectorized scans.
Mental model
A column store groups data by column instead of by row. Reading one column out of many becomes very fast (great for analytics), but writing or updating a single row gets slower. Pick row-stores for transactions, column-stores for analytics.
How to study Columnar Storage
Begin by restating the mental model in your own words, then connect it to a concrete system you have built or operated. Name the mechanism, the constraint it addresses, and the trade-off it introduces. Use Apache Parquet — File format to check details, but close the source before writing your explanation. Retrieval is the learning step; rereading is only preparation.
Next, compare Columnar Storage with Object Storage. Ask what changes in correctness, latency, resource use, operability, and failure recovery. Complete Columnar vs row store and preserve the command, input, output, and one failed attempt as evidence. Finish by explaining the idea without jargon to someone who has not studied the track.
Proof of understanding
- Explain the mechanism from first principles and identify the state it reads or changes.
- Give one situation where the concept is the right choice and one where it is not.
- Predict a realistic failure mode before running the drill, then compare the prediction with evidence.
- Connect the result to a roadmap or build artifact instead of treating the concept as isolated trivia.
Learn from primary sources
Practice and explain it back
Columnar vs row store
Analytics query: SELECT avg(price) FROM sales WHERE date>2024. Which store wins and why?
Expected evidence: Columnar — reads only price+date columns, better compression.
Open the interactive drill →Review prompts
- Why does a column store compress so much better than a row store on the same data?
Build evidence
Use a roadmap capstone to turn this concept into working evidence.