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.
So 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?)
SQLite 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.
Is it? Sqlite seems pretty fast. [1]
[1] - https://andersmurphy.com/2025/12/02/100000-tps-over-a-billio...