4 ms·
Not really. They are two different paradigms. Use the one that is right for you. SQLite is embedded for local applications with one writer mostly. Postgres is
by crazygringo 28d ago
Not really. They are two different paradigms. Use the one that is right for you.
SQLite is embedded for local applications with one writer mostly.
Postgres is for a client-server architecture with many writers.
When you start a project, you generally know which architecture you need.
- andai 28d agoSo if it needs to work offline, but it syncs with a server, then you use both? (And the schema becomes some kind of lowest common denominator?)
- preg_match 28d agoI would probably do an event-source architecture, where you record events on the client and then push them to the server when you're reconnected. It has a lot of benefits, for instance, trivial auditing and free serialization.
- theultdev 28d agoyeah essentially, see electricsql though they also have "pglite" running in wasm. same concept though, sync slices to an embedded db.
- LAC-Tech 28d agoSQLite is embedded for local applications with one writer mostly. In 2026 that advice feels antiquated. SQLite now is absolutely useful now for concurrent, mutli-writer applications. https://www.sqlite.org/src/doc/wal2/doc/wal2.md https://www.sqlite.org/src/doc/wal2/doc/wal2.md
- andersmurphy 27d agoIs it? Sqlite seems pretty fast. [1] [1] - https://andersmurphy.com/2025/12/02/100000-tps-over-a-billion-rows-the-unreasonable-effectiveness-of-sqlite.html https://andersmurphy.com/2025/12/02/100000-tps-over-a-billio...