Wide-column databases are quietly eating the world

TLDR Data's latest post walks through what a wide-column store actually is. Bigtable and Cassandra use the model — wide rows keyed by a primary column, with any number of sparse columns spread across them. It's the difference between a table and a map.

The advantage is real. You can add columns without touching the schema, and queries touch only the columns they need. That's why write-heavy workloads — analytics, time-series data, logs — gravitate toward these stores. They don't need the full relational machinery to be useful.

If your data is naturally wide — one row per user, per device, per session — a wide-column table maps to it directly. If it's narrow and relational, you're paying for columns you don't use.

Why this matters for us: the shift from rigid tables to flexible stores is one of the quieter wins for people running lean — less schema churn, less lock-in, less ops overhead.