3 ms·
Once I discovered SQLite, I never went back. It’s so easy. I’m still shocked when I see docker compose files that spin up entire MySQL dbs when a simple SQLite
by 3fe9a03ccd14ca5 7y ago
Once I discovered SQLite, I never went back. It’s so easy. I’m still shocked when I see docker compose files that spin up entire MySQL dbs when a simple SQLite connector would be so much easier!
- williamdclt 7y agoWhether it is in staging, in dev or in tests, use the same DB engine as in prod. It will save your butt sometimes. Also, my docker-compose for a Postgres container is literally: services: db: image: postgres:10 ports: - "5432:5432" "so much easier" seems very hyperbolic. Not denying that SQLite is an amazing piece of software though!
- jopsen 7y agoHow do you ensure persistence in production? With postgres I just buy a managed setup from heroku, GCP or AWS. Backup is automatic, and there is a follower to takeover if the leader does/crashes. It's easy to backup an sqlite snapshot, but you can't do that after every operation. Curious, how do people solve this?