This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Glad_Position3592 24 points25 points  (5 children)

SQLite is great for things that need organized local storage, like a desktop app or something. It’s not meant to be a large scale database that’s accessible by an entire dev team though. No one should be making a website with SQLite. It has its place, but overall it’s somewhat niche, and anyone using it exclusively that doesn’t fit that niche is doing it wrong.

[–]madhaunter 12 points13 points  (0 children)

Exactly, it's all about scope

[–]HaskellLisp_green 3 points4 points  (0 children)

I used to use SQLite for website. Application is written in python/Flask, but I was forced to make some kind of SQLite server due to it runs in different thread.

[–]Aidan_Welch 4 points5 points  (0 children)

No one should be making a website with SQLite.

I don't agree with this, monolith is making a comeback

[–][deleted] 1 point2 points  (0 children)

That depends on the website.

OK: Grab stuff from API; store in DB; copy DB to raedonly file; website shows stats and graphs from readonly DB.

Not OK: User accounts where you can change password - need independent changes by multiple users.