4 ms·
Are bursting and resizing an issue in the trough, though? GP's premise is that these companies have platform and load stability. There can be marginal gains in
by rhizome 10y ago
Are bursting and resizing an issue in the trough, though? GP's premise is that these companies have platform and load stability. There can be marginal gains in having a dynamic architecture, sure, but when it also costs "months of engineering," I don't see where the savings would be compelling, or even guaranteed.
- QuinnyPig 10y agoThere are companies "in the trough" who are contently spending tens of millions a year on AWS. It's hard to give generic advice for all situations-- as with so much else, context matters heavily. Those marginal gains could potentially pay for a dozen engineers...
- rhizome 10y agoMy point was based on how dynamic the architectures are (or aren't) of those in the trough, not their level of spending.
- QuinnyPig 10y agoAh, my apologies! It depends. I have a toy service that exists entirely as an autoscaling group. That's pretty dynamic! Counterpoint: Mainframes.
- rhizome 10y agoA toy service is not what I'm thinking of as being in "the trough." The trough is where scaling and bursting aren't generally necessary.