Live data from Hacker News

How to Scale a System from 0 to 10M+ Users

blog.algomaster.io

1–10 of 82 posts

Re: How to Scale a System from 0 to 10M+ Users

#3

I really enjoyed reading this. Much like Instagram, which had thousands of users sign up on the first day, if you aren't able to scale because of your skill level, wouldn't that affect usage and lead to comments like: 'The app/site is so slow'?

Aren't comments like "the site is too slow" similar to "the city is too crowded"?

Twitter famously had a "fail whale" but it didn't stop the company from growing. If you have market demand (and I guess advertising) then you can get away with a sub-optimal product for a long time.

Re: How to Scale a System from 0 to 10M+ Users

#4
post #3

I really enjoyed reading this. Much like Instagram, which had thousands of users sign up on the first day, if you aren't able to scale because of your skill level, wouldn't that affect usage and lead to comments like: 'The app/site is so slow'?

Aren't comments like "the site is too slow" similar to "the city is too crowded"? Twitter famously had a "fail whale" but it didn't stop the company from growing. If you have market demand (and I guess advertising) then you can get away with a sub-optimal product for a long time.

Reddit is still around.

Re: How to Scale a System from 0 to 10M+ Users

#5
Not criticizing the core idea, which is sound (don't waste ressource overengineering at the beginning, evolve your architecture to match your actual scale as you grow), but the “number of users” figures in this post are completely nonsensical. You ought to multiply them by 100 (if you're being conservative) or even 1000 (depending on the consumption pattern for the user).

Modern hardware is fast, if you cannot fit more than 100 users (not even 100 concurrent users) on a single $50/month server, you're doing something very very wrong.

Even repurposed 10 years old fairphone[1] can handle more than that.

[1]: https://far.computer

Re: How to Scale a System from 0 to 10M+ Users

#6

Not criticizing the core idea, which is sound (don't waste ressource overengineering at the beginning, evolve your architecture to match your actual scale as you grow), but the “number of users” figures in this post are completely nonsensical. You ought to multiply them by 100 (if you're being conservative) or even 1000 (depending on the consumption pattern for the user). Modern hardware is fast , if you cannot fit m…

Agreed, the numbers were shockingly low.

Re: How to Scale a System from 0 to 10M+ Users

#7

Not criticizing the core idea, which is sound (don't waste ressource overengineering at the beginning, evolve your architecture to match your actual scale as you grow), but the “number of users” figures in this post are completely nonsensical. You ought to multiply them by 100 (if you're being conservative) or even 1000 (depending on the consumption pattern for the user). Modern hardware is fast , if you cannot fit m…

Amazing to see my little phone pop up randomly on hacker news :D

Thank you stranger.

Re: How to Scale a System from 0 to 10M+ Users

#8

I really enjoyed reading this. Much like Instagram, which had thousands of users sign up on the first day, if you aren't able to scale because of your skill level, wouldn't that affect usage and lead to comments like: 'The app/site is so slow'?

It depends on the adoption model.

If it’s just “sign up any time you want and go”, yes, it can go that way.

If it’s “join that waiting list” or “book a call” (for KYC purposes or whatever), you have a buffer.

If user count is more or less constant (most internal websites, for example), it’s probably not an issue.

And so on.

Re: How to Scale a System from 0 to 10M+ Users

#9
post #3

I really enjoyed reading this. Much like Instagram, which had thousands of users sign up on the first day, if you aren't able to scale because of your skill level, wouldn't that affect usage and lead to comments like: 'The app/site is so slow'?

Aren't comments like "the site is too slow" similar to "the city is too crowded"? Twitter famously had a "fail whale" but it didn't stop the company from growing. If you have market demand (and I guess advertising) then you can get away with a sub-optimal product for a long time.

I agree. Go fast with a suboptimal architecture. If success arise, throw away version 1 and rebuild from scratch. Often is more effettive.
Post reply on HN