3 ms·
If scaling up is painful there is something wrong with the architecture. Aside from this scenario, what if you just get a spike in traffic? If your scaling solu
by tus88 7y ago
If scaling up is painful there is something wrong with the architecture. Aside from this scenario, what if you just get a spike in traffic? If your scaling solution can't handle it, get a better one, otherwise what's the point?
- saagarjha 7y agoPresumably servers take time to boot and initialize, which is still a problem if you get a spike but those aren't as sudden as "everything just turned back on".
- bostik 7y agoYup, in a reasonably, but not entirely optimised setup, the spinup time for a new node from scale-up event launching to it being able to serve traffic may take 2-3 minutes. And trust me, after a couple of mishaps with very aggressive scale-ups, your system will not launch the full demand absorption all at once. In a fully optimised setup each service image is itself 100% preconfigured, and only provisions node secrets during the boot. Even one of these types of nodes takes easily 30-40 seconds from launch event to actually serve traffic: it may join the load balancer just 25 seconds in, but the load balancer will want to see at least two good health checks before allowing any traffic to it. The problem with aggressive upscaling in the depicted scenario is that your plumbing layer is also likely scaled down. Hitting it with a cascade of new nodes has the risk of going all thundering herd, crippling the system for both existing and new nodes.