[HN Gopher] DuckDB in Action
___________________________________________________________________
DuckDB in Action
Author : tosh
Score : 21 points
Date : 2024-03-18 14:40 UTC (8 hours ago)
(HTM) web link (www.manning.com)
(TXT) w3m dump (www.manning.com)
| boxcarr wrote:
| Motherduck.com has a pop-up promotion to get the book for free.
| vladsanchez wrote:
| https://motherduck.com/duckdb-book-brief/
| timenova wrote:
| Does anyone know how well does DuckDB's persistent mode compare
| to SQLite for example?
|
| Does it write synchronously on COMMIT and never lose data? Is it
| reliable enough to use instead of SQLite?
| r1cka wrote:
| DuckDB targets analytical workloads. Your question sounds like
| your workload is transactional to me, so I'd recommend sticking
| with SQLite.
| cipherzero wrote:
| Agree, in fact this wonderful book calls this out, stating:
| As DuckDB is an analytics database, it has only minimal
| support for transactions and parallel write access. You
| therefore couldn't use it in applications and APIs that
| process and store input data arriving arbitrarily. Similarly
| when multiple concurrent processes read from a writeable
| database.
| overbytecode wrote:
| How do you decide when to reach for Polars vs DuckDB?
| jasonjmcghee wrote:
| In Python, I think of them as, DuckDB is for getting the data
| you want, in the form you want it, from a file / remote place.
| Polars is for when you want to do something with that data,
| like visualize it.
|
| `duckdb.sql("SELECT foo, bar * 2 as bar_times_2 FROM
| ...").pl()` (now in polars format) -> other stuff
|
| In Rust, it's a bit fuzzier to me, as DuckDB is a pretty heavy
| dependency. I'm looking more and more fondly at DataFusion.
| lvl102 wrote:
| DuckDB is nice but I'd like to see some alternatives to RAPIDS in
| the GPU space.
___________________________________________________________________
(page generated 2024-03-18 23:02 UTC)