3 ms·
"column oriented database" We all have our specialties, and that is fine. It is a common pattern that a developer gets comfortable with a particular tech stack
by lkrubner 4y ago
"column oriented database"
We all have our specialties, and that is fine. It is a common pattern that a developer gets comfortable with a particular tech stack, and then uses it for many years without seeing the need for much else. Some developers use Ruby on Rails plus Postgres for everything, others use C# and .NET and SQL Server. It's fine, if that's all you need.
Still, this is the year 2022. Cassandra, to take one example, was released in 2008. For everyone who has needed these fast-read databases, they've been much discussed for 14 years, including here on Hacker News, and on every other tech forum. At this point I think a company can simply assume that most developers will have some idea what a column database is.
- ipaddr 4y agoYou never explained what a column database is. One row and unlimited columns?
- asah 4y agohttps://www.google.com/search?q=columnar+database https://www.google.com/search?q=columnar+database
- cachemiss 4y agoCassandra is not a columnar database, columnar in this sense is about the storage layout. Values for a column are laid next to each other in storage, thus allowing for optimizations in compression and computation, at the expense of reconstructing entire rows. Postgres is a row store, meaning all the columns for a row are stored next to each other in storage, which makes sense if you need all of the values for a row (or the vast majority).