3 ms·

SQLite can start to show weaknesses when you need a bunch of people or processes writing to it at the same time. For small applications or applications where yo

SQLite can start to show weaknesses when you need a bunch of people or processes writing to it at the same time. For small applications or applications where you can tightly control what is talking to it at any given time, SQLite is great. Enterprise products tend to target larger organizations where a more overengineered solution is likely commonly available anyways. Generally though, I want developers to justify why SQLite isn't good enough for their app before they build on something else. In a lot of cases SQLite absolutely is good enough, and it removes an insane amount of complexity, especially from things like database backups.

willsmith72 3y ago
i tend to lean the other way. postgres is just so easy. with managed db services, you dont have to think about backups, version upgrades, all the rest. you never have to worry about running into a rough edge or missing feature. the maturity and huge community make it hard to go wrong
- tracker1 3y ago
  Agreed... As soon as you need shared access to multiple systems, PG it is, usually in Docker though if it doesn't need a dedicated instance. Though I have used Firebird when I needed to scale it support local and remote data before. I don't think Figured gets nearly enough attention.
tracker1 3y ago
I remember really pushing for SQLite for a specific application that used MS SQL... The main data in practice has requirements to be archived by event. And didn't need more than a few dozen users with low transactions in practice. Easy backup, archive etc. In the end, there was a complex solution with a all the business logic in stored procedures and functions. With a lot of variability and difficulty supporting the application. This was for a petition verification system. So each petition could have easily fit into a SQLite database. Been portable and easy to archive, backup, transport etc. But no,. We had to put all the logic in the database... Because integritai...

willsmith72 3y ago

i tend to lean the other way. postgres is just so easy. with managed db services, you dont have to think about backups, version upgrades, all the rest. you never have to worry about running into a rough edge or missing feature. the maturity and huge community make it hard to go wrong

tracker1 3y ago
Agreed... As soon as you need shared access to multiple systems, PG it is, usually in Docker though if it doesn't need a dedicated instance. Though I have used Firebird when I needed to scale it support local and remote data before. I don't think Figured gets nearly enough attention.

tracker1 3y ago

I remember really pushing for SQLite for a specific application that used MS SQL... The main data in practice has requirements to be archived by event. And didn't need more than a few dozen users with low transactions in practice. Easy backup, archive etc. In the end, there was a complex solution with a all the business logic in stored procedures and functions. With a lot of variability and difficulty supporting the application. This was for a petition verification system. So each petition could have easily fit into a SQLite database. Been portable and easy to archive, backup, transport etc. But no,. We had to put all the logic in the database... Because integritai...