If your job requires something that SQLite doesn't provide, then sure, that's the wrong tool for the job. But SQLite is literally the most frequently used data

If your job requires something that SQLite doesn't provide, then sure, that's the wrong tool for the job. But SQLite is literally the most frequently used database in the world so it clearly is the right tool for a large number of jobs. It's a very fast and very capable database and the reliability is unmatched (because it has been the most tested and because Richard Hipp wrote more tests than anyone else). There's this persistent myth that SQLite is some rinky dinky toy for toddlers. I repeat: it's very fast, very capable database, more than capable of addressing 97% of the needs of people who use sql databases. What bothers me about this kinds of "SQLite is not the right tool" assertions is a complete lack of any supporting evidence. Like, give me an example of something that you're doing where Postgres or MySqlite offers meaningful improvement over SQLite. I'm not saying those cases do not exist, just that they are much rare that people tend to assert and you haven't provided a single example. Pieter Levels runs highly profitable, highly trafficked website (Nomad List) on sqlite and he doesn't even write joins. And my point is that you vastly overestimate the need for super duper advanced functionality in databases. Lots of apps were written on top of early MySQL, which was a joke in terms of both capabilities and reliability. SQLite today is more capable and reliable that MySQL was for a long time.