Hacker News Reader

Comment by erulabs | Hacker News Reader

See I’ve been using Vitess on Kubernetes for even personal projects and I gotta say I love that I can run, for 10 bucks a month on Linode, the same tools that I know by experience I can scale to a multi-billion dollar valuation worth of customers. Heck I even run it in development on my laptop thanks to Skaffold.

Sure it’s all insane overkill - but I use Linux for the same reasons - I want one API that I can use everywhere, from my toaster to my spaceship, from hobby to enterprise.

The simplicity is not the API. The simplicity is having one API.

View on HN

AFAIK, you can only buy 2 smallest nodes with $10 on Linode, how do you create a k8s cluster with that?

You also run a company which offers kubernetes self hosting as a business, which is quite the bias.

Anyways, the question isn't whether client-server databases scale, it's whether SQLite doesn't scale. What were the database size, resource constraints, architecture for the multi-billion $ company? How did this scale over tiem? Do you have any reason to believe that a SQLite architecture couldn't scale to support the service offerings you saw?

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.

Google reportedly receives 99k search queries per second - which company actually handles 6 digit QPS reads?

Well 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!

Reply on news.ycombinator.com