4 ms·

Simple, you usually don't need that. Most devs now a days don't know how to build efficient websites. That's why they need a tech Stack like the Mount Everest a

by Mave83 5y ago

Simple, you usually don't need that. Most devs now a days don't know how to build efficient websites. That's why they need a tech Stack like the Mount Everest and create a dependency hell. It was possible to serve more then 250k unique users per day from a single VM more than 10y ago on shitty hardware. You can deliver so much more on modern tech if you stick to KISS principle. But yes, some rare sites do need to scale above >1M unique users, that's where the trouble begins. You can start by benchmarking everything you build. Think of every line of code and optimize it, or you just build your stack in smaller pieces and scale out using modern tech Stack. The question is, what do you want to learn. The first way would learn you how to build efficient software, the second one would teach you how to waste lots of resources but be new, modern and a hipster. And in addition, now a days employees are so expensive, that a company don't care about Cloud costs if this makes dev faster.

cunac 5y ago
not to be rude but 250K uniques users is 3 new users per second and doesn't say anything about concurrent users. Concurrent users are scaling problem
- vanusa 5y ago
  There's a natural distribution to these things, so actually an average of 3 does in fact say "something" about the tail behavior of concurrents (that is, the highest values you can expect under peak load). As a rule of thumb: it's probably on the order of 5x-10x (absent outlier events); then look at your data to find out what it actually is (users are not evenly distributed across the day/week); then apply the usual 4x or so rule for capacity planning. That is to say - it isn't necessarily a scaling issue. Especially when you're just starting out and no one is looking at your damn app anyway. If it's well designed and cleanly built you'll have plenty of time to factor for scale when the time comes (if it comes).

by Mave83 5y ago

cunac 5y ago

not to be rude but 250K uniques users is 3 new users per second and doesn't say anything about concurrent users. Concurrent users are scaling problem

vanusa 5y ago
There's a natural distribution to these things, so actually an average of 3 does in fact say "something" about the tail behavior of concurrents (that is, the highest values you can expect under peak load). As a rule of thumb: it's probably on the order of 5x-10x (absent outlier events); then look at your data to find out what it actually is (users are not evenly distributed across the day/week); then apply the usual 4x or so rule for capacity planning. That is to say - it isn't necessarily a scaling issue. Especially when you're just starting out and no one is looking at your damn app anyway. If it's well designed and cleanly built you'll have plenty of time to factor for scale when the time comes (if it comes).