3 ms·
That's really pushing SQLite where it was clearly not engineered to go. If you need something that is accessible over the network, use a database server that is
by RedShift1 5y ago
That's really pushing SQLite where it was clearly not engineered to go. If you need something that is accessible over the network, use a database server that is designed for it. The right tool for the right job.
- er4hn 5y agoNonsense. Just be like the Tailscale team and use SQLite [1] to serve your entire customer network. [1] https://tailscale.com/blog/database-for-2022/ https://tailscale.com/blog/database-for-2022/
- jpalomaki 5y ago"SQLite does not compete with client/server databases. SQLite competes with fopen()." https://www.sqlite.org/whentouse.html https://www.sqlite.org/whentouse.html
- jhgb 5y agoFirebird can do both, though.
- mekster 5y agoI often see this quoted but I don't see how they compete at all? Or am I just not getting a joke?
- antifa 5y agoI have seen a lot of enthusiasm for using sqlite instead of postgres for django/laravel/rails type projects, or just using it for your tests. I think both of these opinions are over valued since it's easier to learn postgres once then to learn sqlite then migrate to postgres. The real developer cost of "install postgres, createuser, createdb" is basically nothing. I see the cost of ever using sqlite (coupling my tests/and/or app, migrating as soon as you have 2 users) as much higher. Sqlite does seem like a safe, solid, and sane default for the embedded/fopen people though.