Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- This is a bait and switch article. Compare apples and oranges, "oh btw look at our product".by oathvz
- I couldn't read the article as it read like AI.
And I am fatigued by the AI style in all code comments, reviews, PRs etc :(
by k3liutZu - Title, which is already synthetic, should be "Choose DuckDB rather than SQLite for Analytics Workloads".by tptacek
- How are these two DB engines even comparable other than at the edges? They handle two completely separate workload types: one is more a general-purpose DB engine and the other is specifically for columnar datasets, analytics and the like -- of course a hand-tuned DB engine is going to destroy SQLite on any reasonable benchmark: SQLite wouldn't be optimized for that hand-tuned use-case whereas something like DuckDB is.by ethin
- Despite its obvious advantages, the biggest drawback of DuckDB is its concurrency model [1]. If a process opens a database in read-write mode, it acquires an exclusive lock on the file. This prevents even simple read operations from other processes as long as the writer remains open. Maybe there's a simple workaround I haven't come across, but I found it to be quite a productivity killer.
So yes, all these benchmarks are great, but it wasn't so fun working with DuckDB when I had to close duckdb cli, just so a query in another script could run.
by shubhamjain - > DuckDB's columnar engine
That is workload specific. Title should be "Choose DuckDB rather than SQLite for Analytics" IMHO
by brightball - This is AI slop, but I really want to know more about their write patterns and how they were doing batches.
- AI slop. The content might be valuable but the framing makes it too painful to read.
Please, folks, write with your own voice -- especially if it's for your business blog. It's good for you as an author (practice makes perfect) and it's good for your readers (whom you want to influence).
by otterley