Not every SMB panel needs a PostgreSQL cluster from day one. Prisma with SQLite can be appropriate for a single application server, low write concurrency and a measured query load. Directly copying a live database file during writes does not guarantee a consistent backup; use the SQLite backup API, a controlled snapshot or an application-stop method as appropriate, keep the copy in a separate location and test restoration.
SQLite's limits
- High concurrent write demand
- Multiple app servers writing the same DB file
- A DB file on networked NFS
- Write locks during heavy reporting queries
Migration signals
If SQLITE_BUSY climbs, a second app server is planned, or reports stall live traffic, move to Postgres. The Prisma schema mostly ports; the real work is connection string, migrations and backup procedure.
Assess database choice against the current workload, tolerance for data loss, maintenance responsibilities and growth plans. Define restoration testing, capacity monitoring and the scope of any future database migration as separate items in the proposal.
