[brightball]

> DuckDB's columnar engine

That is workload specific. Title should be "Choose DuckDB rather than SQLite for Analytics" IMHO

[dangoodmanUT]

This. The title might as well be “Choose a hammer rather than a wrench (when driving nails)”

[ray_v]

Yes - it's a specific workload for sure. SQLite is still the GOAT when it comes to OLTP, but DuckDB is really becoming the GOAT in the OLAP world - I think DuckDB is simply amazing and truly an amazing piece of technology for anyone working with large amounts of data.

[dataviz1000]

> SQLite is still the GOAT when it comes to OLTP, but DuckDB is really becoming the GOAT in the OLAP world

Can you explain this more, especially why SQLite is best at OLTP and what happens at scale?

[storywatch]

Most people forget that clickhouse embedded exists

[iw2rmb]

Let's keep discussion bar high.

I've just checked their website, and they state "relying on ClickHouse to power these analytics use cases". That's not OLTP. https://clickhouse.com/comparison/postgresql

Fair to say, seeing 1000x w/o any trace of proof won't help me to choose.

[misiek08]

You new to the world, right? ClickHouse proven being a beast for analytics, tracing and even some basic metrics storage (VM won of course, but still CH is probably 2nd or 3rd)

[storywatch]

* for other readers, VM here most likely refer to Victoria Metrics

[iw2rmb]

Every day someone is new to the world. Analytics is not OLTP. Would appreciate for anything to read except “you stupid” and “believe me, bro”.

[adsharma]

DuckDB also implements MVCC. In DuckLake, the DB is used for absorbing small writes and compacting them before sending to object storage.

It has some characteristics typical of OLTP engines. But they are targeted and limited to areas DuckDB feels are important.

[cognitiveinline]

Yeah, someone who has more tokens than simple sense.