Every job is evolved over time from tools to missions. For example, I was using Visual Basic 6.0 to develop a single-server software on Windows XP about 20 years ago, but now I'm using Golang and many other tools to develop web-based and Serverless services in the Cloud. I'm sure the job description of DBA is being redefined too. As a contributor to https://bytebase.com/, we are hoping to provide a tool to DBAs by offering a web-based collaboration workspace to help DBAs and Developers manage the lifecycle of application database schemas (DDL) and data (DML).

Postgres is much heavier than SQLite in terms of binary size/CPU/RAM, but I think scalability is the win.

OTOH if you don't tune it the default postgres configuration remains extremely low-resource (which also hampers its performances): 128MB shared buffers, 8MB temp buffers, 4MB work_mem, 64MB maintenance_work_mem, 100 connections, 1000 files open.

Compared to less than 1MB for sqlite in this use case.

Totally agree, compatibility is really the key for any database product or any product. Minimizing the migration gap helps adoption.