Quack-reduce author here. I think the most interesting thing about duckDB (for us) is that you can "take out the DB" from duckDB and use the built-in engine ov

Quack-reduce author here. I think the most interesting thing about duckDB (for us) is that you can "take out the DB" from duckDB and use the built-in engine over a (stateless, ephemeral) table you got from wherever. We didn't do much map-reduce aside some quick tests (i.e. the ones in that repo), but we did pursue a larger vision for serverless lake-house in which SQL and Python co-exist and data flow seamlessly between functions and across languages. In case you're curious, we have a vision paper out and always happy to chat: https://arxiv.org/pdf/2308.05368.pdf https://arxiv.org/pdf/2308.05368.pdf