> There would genuinely be more maintenance required for the PostgreSQL server/daemon than the application itself. It just makes no sense. I think this is the

> There would genuinely be more maintenance required for the PostgreSQL server/daemon than the application itself. It just makes no sense. I think this is the key point the original post was missing. When you’re working on a project with a DB, you should factor in the cost/overhead of the DB as well. Postgres is a wonderful DB. But it is also big and requires work to keep it running. For many projects, the extra overhead is well worth it. (And if you’re using a “cloud” DB, the overhead is still there, but you’re explicitly paying for the privilege of making it someone else’s problem. ) But for smaller projects, or ones with less DB requirements, something small like SQLite is much more appropriate. And it nearly removes the DB overhead from the maintenance equation.