Iceberg for the win!
We actually separate Read/Write paths. BemiDB reads by levering DuckDB as a query engine. And it writes to Iceberg completely separately from DuckDB. I'm curious if that's what you imagined.
Ideally, I would love many places writing to the Iceberg catalogue and then using it as a data lake.
In the data lake, I would have a gateway provisioning DuckDB on demand for each user.
Ideally, I would love many places writing to the Iceberg catalogue and then using it as a data lake.
In the data lake, I would have a gateway provisioning DuckDB on demand for each user.