4 ms·
Why not just use an autoscaling group? Re: cleverness trap. I feel like this is the tragedy of software development. We like to be seen as clever. We are doing
by x86x87 3y ago
Why not just use an autoscaling group?
Re: cleverness trap. I feel like this is the tragedy of software development. We like to be seen as clever. We are doing "hard" things. I have way more respect for engineers that do "simple" things that just work using boring tech and factor in whole lifecycle of the product.
- p_l 3y ago> Why not just use an autoscaling group? Not everyone has money to burn, even back in ZIRP era. And before you trot out wages for experienced operations team - I've regularly dealt with it being cheaper to pay for one or two very experienced people than deal with AWS bill. For the very simple reason that cloud provider's prices are scaled to US market and not everyone has US money levels.
- Spivak 3y agoSorry, I could have explained that better. The biggest value add that k8s has is that it gives you as many or as few autoscaling groups as you need at a given time using only a single pool (or at least fewer pools) of heterogeneous servers. There's lots of fine print here but it really does let you run the same workloads on less hardware and to me that's the first and last reason you should be using it. I wouldn't start with k8s and instead opt for ASGs until you reach the point where you look at your AWS account and see a bunch of EC2 instances sitting underutilized.