new | show | ask | jobs Github

brightball 2 hours ago

> DuckDB's columnar engine

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

▲

dangoodmanUT 2 hours ago | parent | next [-]

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

▲

ray_v 2 hours ago | parent | prev | next [-]

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 2 hours ago | parent [-]

> 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 2 hours ago | parent [-]

Most people forget that clickhouse embedded exists

	▲	iw2rmb 44 minutes ago \| parent [-]
		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.

▲

adsharma an hour ago | parent | prev | next [-]

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 2 hours ago | parent | prev [-]

Yeah, someone who has more tokens than simple sense.