From what I understand Ducklake needs a dedicated metadata database and it also ties to DuckDB land wherease with Iceberg many engines can query directly.
You are already using Postgres in your setup so why not just use Postgres itself as metadata database? It is a much better setup than using Iceberg [1].
> and it also ties to DuckDB land wherease with Iceberg many engines can query directly.
Ducklake can also be queried by many engines [2]. Though not as exhaustive as Iceberg.
> and it also ties to DuckDB land wherease with Iceberg many engines can query directly.
Ducklake can also be queried by many engines [2]. Though not as exhaustive as Iceberg.
[1]: https://www.youtube.com/watch?v=-PYLFx3FRfQ [2]: https://ducklake.select/docs/stable/#list-of-ducklake-client...