3 ms·
“sqlite per actor” feels like very clean actor level isolation. the part I am more curious about is how you recommend handling cross actor queries.
by swaminarayan 8mo ago
“sqlite per actor” feels like very clean actor level isolation. the part I am more curious about is how you recommend handling cross actor queries.
- NathanFlurry 8mo agoWe built everything with this architecture internally already at Rivet. It's less common than you might expect to have to query cross-DB in practice. However, we are planning on building a query engine that can operate over multiple databases. One option we're considering is exposing Rivet SQLite as a DuckDB datasource: https://duckdb.org/docs/stable/data/data_sources https://duckdb.org/docs/stable/data/data_sources