5 ms·
You're right, and that might be a good choice if you wanted to deploy and operate an additional PostgreSQL server locally. ## Using DuckDB: app -> duckdb -> n
by lukekim 2y ago
You're right, and that might be a good choice if you wanted to deploy and operate an additional PostgreSQL server locally.
## Using DuckDB:
app -> duckdb -> network -> remote postgres (data)
|
local postgres (materialization)
## Using Spice:
app -> localhost gRPC/HTTP -> [Spice <duckdb|sqlite>] -> network -> [postgres|S3|snowflake|etc]
In addition, Spice manages the materialization for you. In the DuckDB-only case, you'd have to do a COPY FROM [remote postgres] to [local postgres] manually every time, and manage the data lifecycle yourself. That gets even more complicated if you want to do append or incremental updates of data to your local materialization.