3 ms·
Why SQLite instead of a standard hub and spoke replication? What benefit does this provide? Being able to run your database on the client? That seems like it wo
by packetlost 3y ago
Why SQLite instead of a standard hub and spoke replication? What benefit does this provide? Being able to run your database on the client? That seems like it would be risky
- tptacek 3y agoBecause it’s running in the app’s address space, SQLite is obscenely fast for reads, so much so that you can often just write N+1 queries with it.
- hamandcheese 3y agoIn this case though it appears that SQLEdge is running as its own process, distinct from the app, and the app sends all queries to the SQLEdge proxy.
- tptacek 3y agoThat makes less sense to me then, though the IPC cost for those reads is still much lower than a typical n-tier Postgres setup.