Comparison
SQLite and PostgreSQL: deployment models
Understand the architectural difference between an embedded database and a database server before comparing individual features.
At a glance
- SQLite
- Embedded database engine
- PostgreSQL
- Client/server database
Overview
SQLite and PostgreSQL both provide SQL databases, but their deployment models differ. SQLite runs within an application and reads local database files. PostgreSQL is a database server. The SQLite project's usage guidance explains when embedded storage fits and when a client/server database is more appropriate.
Where embedded storage fits
SQLite's usage guide describes local application storage, device software, and other cases where data sits with the application. A separate database service is unnecessary for those arrangements, reducing the number of moving parts an application must operate.
When to consider a server
The same guide points toward client/server systems for many concurrent writers or situations where clients reach a database over a network. Treat this as an architectural choice: workload, access patterns, and operations matter more than a universal winner.
Sources and review
MOOR's explanatory text is supported by the following source links.
- Appropriate Uses For SQLite — SQLite
- SQLite and PostgreSQL: deployment models: supporting documentation — PostgreSQL Global Development Group