Jason Lemkin

And think about that, like, it's not about writing transactions to a database.

It's all about, you have a million and now maybe a billion or 10%.

billion data elements there, and you want to quickly scan down a column and add them all up.

How many clicks?

How many people traversed your website?

Large amounts of typically read-only data.

And if you use a standard snowflake database, it's fairly inefficient.

Because that's written to be able to write transactions where you write in a transaction.

Like here's my typically, you know, a debit or credit.

So Snowflake's optimized for that.

And Columbo databases like ClickHouse are optimized for analytics processing.

It's a different category of database.

And, you know, data warehouses back in the 90s and 2000s, the same thing.

You have your production database where you run your system, your banking system, your ERP, your PIC, you know, whatever it is.

And then you have this analytical database.

place where you put off all the transactions.

Because some analyst is going to wake up and say, I have a really obscure question.

How many people bought this product in this district two days after they did this online on the website?

I need to know how many people did that, because I want to do attribution.

Some weird corner case like that.