I like SQLite (use it for android apps), but there’s no reason to use it for apps over a network. SQLite is meant to be embedded (also works great with desktop apps and local-only web apps).<p>In fact, I’d argue there’s no <i>networked</i> use case in which SQLite is cheaper, easier to deploy, maintain or run than Postgres.<p>All that being said, absurdsql is great. There should be some optimizations in mirroring network state to IndexedDB that could be queried via SQl(ite).<p>The SQLite documentation literally says use Postgres and not it for networked use cases (unless you use WAL or rollback, in which case why not just use Postgres?)<p><a href="https://www.sqlite.org/useovernet.html" rel="nofollow">https://www.sqlite.org/useovernet.html</a><p>—-<p>As an aside, I think we need a new storage primitive. In the 2000s desktop apps were rampant and SQLite was more or less the standard.<p>We then moved over to networked apps where RDBMS had its day. There was a moment where nosql was booming for the scaling but it turned out people like relations.<p>We need an open source, distributed and relational store that’s easy to maintain build this decade.