3 ms·
> Instead if you kept the same 6 engineers around for decades you could probably scale to 100m with those same engineers. Scaling to 100m users is more about y
by toast0 3y ago
> Instead if you kept the same 6 engineers around for decades you could probably scale to 100m with those same engineers.
Scaling to 100m users is more about your users/product than your engineering IMHO.
If your product doesn't appeal to 100m users, you can't scale that high. It's not necessary to be ready for usage that's unrealistically high. And your team won't develop experience scaling if it's not happening.
Mega scaling gets more approachable all the time. Ebay had to shard their databases pretty early, because what they could fit on the biggest Sun machine to run Oracle they could buy isn't much. Now you can run a dual socket Epyc and get 256 cores with terrabytes of memory and petabytes of storage in one system. Might not be the best way to run your database, but if your queries aren't super awful, you can do a ton of queries per second with that much ram.
- rmbyrro 3y agoThe discussion is implicitly based on the assumption that the product can attract 100M users and the engineering challenges arise from that