SQLite is very limited because of its threading model, imo it's not usable outside of the single app model where you have a single user. It lacks robust concurrency, doesn't scale well under high write loads, and can become a bottleneck in multi-user or web environments. If you are thinking about using it just go with a reliable DB like Postgres or mySQL.

>>105972247 (OP)
People use it in browser-based applications and simple personal projects. It's about picking the write tool for the job. Postgres isn't needed for the a chore app that some hobbyist runs on their Raspberry Pi.

>>105972292
There are people suggesting that 99% of all websites only need to use SQLite. This type of statement is what I'm trying to address.

>>105972324
This is probably not far from correct. The average website likely has so little traffic that an SQLite db would more than suffice. For you to need anything more you'd need a high traffic site with a need to store a lot of data constantly, like 4chan or Amazon.

>>105972324
>There are people suggesting that 99% of all websites only need to use SQLite.
That is correct, yes. The vast, vast majority of websites serve information and don't allow any writes at all, and are serving <100 users at a time. SQLite is completely adequate for that.

>>105972544
To be clear: I'm not saying you SHOULD use it, I'm just saying most websites COULD because their traffic is so low.

>>105972388
4chan doesn't need a database for anything outside of logins, and those should be handled by an auth server
there are what, 120 boards, 150 threads per board, that's 18K plain html pages
your general file system can handle that
there's no search function on here, so just append the right thread when a post is submitted and the date modified on the file determines which is the oldest to be pruned
4chan should be one of the easiest websites to build if you think about it

>>105973495
Where are you storing cookies?

>>105972247 (OP)
>tfw when you’re JavaScript web app is so bloated you need a dedicated Postgres Server because you can’t write code that can function with a single threaded SQlite database.

>>105973495
4chan could be ran on SQLite

>>105974060
could be run*

>>105972247 (OP)
1. SQL in general doesn't "scale" well because CAP theorem
2. The solution is to shard the SQLite database and manage organization yourself on the filesystem, rather than a daemon and scheduler doing it for you.

>>105972247 (OP)
Which one does it support inserting images?

>>105975135
Just store the image data bro

>>105975421
Like a BLOB.
I realized that.
what about videos?
Also that way the database can go realllly big in size like easily 50 GB+
How would this work by then?

>>105975630
If you're concerned about it, store the media on a an S3 bucket or something

>>105975645
No, I want it all locally.
>S3 bucket
How much should I pay?

>>105972247 (OP)
>>105973622
Strapi defaults to SQLite