Hacker News new | past | comments | ask | show | jobs | submit login

Because 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.



In 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.


That makes less sense to me then, though the IPC cost for those reads is still much lower than a typical n-tier Postgres setup.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: