4 ms·
If you’re exceptionally careful and skilled about writing smart queries, SQLite can for sure scale to the point you can afford to resign anything you want. The
by erulabs 4y ago
If you’re exceptionally careful and skilled about writing smart queries, SQLite can for sure scale to the point you can afford to resign anything you want. The idea behind vitess and sharded MySQL (and for that matter kubernetes too) is that you can move fast and not make a terrible mess of things. I can split off one poorly designed table with Vitess - with SQLite that would be an application redesign.
But in general I compare the intended scale to successful startups I’ve been at - where several TB of data are being read by hundreds of thousands of users per second. Typically this requires a fleet of the largest instance types most cloud providers offer.
Anyways - you’re not wrong and neither is the author - but if I’m going to choose one tool - I’d rather it work for all intentions and be a bit more complex than the other way around.
- srcreigh 4y agoGoogle reportedly receives 99k search queries per second - which company actually handles 6 digit QPS reads?
- erulabs 4y agoWell if you're talking about a single query, virtually no one hits that scale. But in terms of over-all QPS in quickly-scaled apps, 6 digit QPS is super common. All it takes is a poorly programmed notification or messaging feature to hit that number. Also, that was for sure a high-water mark, not the typical usage!