2 ms·
So about one per second (up to ten, less conservatively). I concur. But if you think your site might ever scale beyond that, do yourself a favor and use Postgre
by inigyou 4mo ago
So about one per second (up to ten, less conservatively). I concur. But if you think your site might ever scale beyond that, do yourself a favor and use Postgres from the get-go.
- rafabulsing 4mo agoThe vast, vast majority of websites never see anything even close to that, so it's a safe bet unless you have some specific reason to expect it to reach that kind of traffic, or you are dealing with workloads that SQLite really does not handle well, e.g. many concurrent writes. And if your workload is mostly reads, then you probably can use a cache layer, which allows SQLite to go further still.
- maccard 4mo agoAdding a cache layer to keep using the wrong database is an architecture failure - if you use Postgres from the get go you will not need the cache until way way later on anyway. (Side note, I’m team MySql but the same point applies)
- rafabulsing 4mo agoWhat exactly is wrong about a solution that perfectly fits the most common use case out there, at a fraction of the cost/complexity?
- simonw 4mo agoSQLite can happily handle thousands of reads and writes per second even on modest hardware.
- dukeyukey 4mo agoThey also say it seems to work well up to 500k a day, which is quite a bit.
- noxer 4mo agoI have 8+ million rows added daily to a 100+GB DB. There is a limit somewhere but I haven't found it yet.