3 ms·

I can't help but wonder if devs feel this way because several full stack web frameworks default to using SQLite in their dev environment. That, and the name ("l

I can't help but wonder if devs feel this way because several full stack web frameworks default to using SQLite in their dev environment. That, and the name ("lite"). Of course that's not at all true, SQlite is an incredibly robust production-grade tool that is deployed to billions of devices, but it sure feels like that caused damage to the brand. That said I think this is actually becoming less of an issue these days. Certainly feels like there has been a resurgence in SQLite appreciation and usage over the past few years.

acuozzo 2y ago
> That, and the name ("lite"). It's SQLite like a mineral. Pyrite, for instance. SQL-ite, not SQ-lite.
- zamadatix 2y ago
  It "is" (that's how the creator originally thought about it) but it also isn't really prescribed as the only interpretation https://www.youtube.com/watch?v=Jib2AmRb_rk&t=50s https://www.youtube.com/watch?v=Jib2AmRb_rk&t=50s Though I'll also note the "lite" crowd often interpret the "L" as double duty/shared (like the "m" in "dramedy" isn't necessarily interpreted as solely part of "drama" or "comedy").
erik_seaberg 2y ago
Production-grade data needs to be redundant across regions to outlive a disaster. I was glad to hear that SQLite replication exists, but it's an add-on (Litestream) that isn't strongly consistent nor multi-master.
- dcchambers 2y ago
  For a SaaS product? Maybe - but even that's debatable. I imagine snapshots/backups stored off-site/in other regions are more than fine for the majority of SaaS businesses - certainly almost all businesses under a certain size. Sure you risk some minor data loss in a true disaster (like, meteor hits a datacenter disaster), but generally I think your odds are pretty good. But that's just a subset of what databases are useful for. So much production data lives on-device with no replication or redundancy at all. It's still production-grade data. https://www.sqlite.org/mostdeployed.html https://www.sqlite.org/mostdeployed.html
a96 2y ago
Although the common technical meaning of "light" is low resource usage, small footprint and overhead. Opposite of massive or convoluted in the sense of heavy.

acuozzo 2y ago

> That, and the name ("lite"). It's SQLite like a mineral. Pyrite, for instance. SQL-ite, not SQ-lite.

zamadatix 2y ago
It "is" (that's how the creator originally thought about it) but it also isn't really prescribed as the only interpretation https://www.youtube.com/watch?v=Jib2AmRb_rk&t=50s https://www.youtube.com/watch?v=Jib2AmRb_rk&t=50s Though I'll also note the "lite" crowd often interpret the "L" as double duty/shared (like the "m" in "dramedy" isn't necessarily interpreted as solely part of "drama" or "comedy").

erik_seaberg 2y ago

Production-grade data needs to be redundant across regions to outlive a disaster. I was glad to hear that SQLite replication exists, but it's an add-on (Litestream) that isn't strongly consistent nor multi-master.

dcchambers 2y ago
For a SaaS product? Maybe - but even that's debatable. I imagine snapshots/backups stored off-site/in other regions are more than fine for the majority of SaaS businesses - certainly almost all businesses under a certain size. Sure you risk some minor data loss in a true disaster (like, meteor hits a datacenter disaster), but generally I think your odds are pretty good. But that's just a subset of what databases are useful for. So much production data lives on-device with no replication or redundancy at all. It's still production-grade data. https://www.sqlite.org/mostdeployed.html https://www.sqlite.org/mostdeployed.html

a96 2y ago

Although the common technical meaning of "light" is low resource usage, small footprint and overhead. Opposite of massive or convoluted in the sense of heavy.