4 ms·
you MIGHT save money. The price difference can be substantial enough that you might simply be better off having it "over provisioned" off hours. Also, not hav
by latch 8y ago
you MIGHT save money.
The price difference can be substantial enough that you might simply be better off having it "over provisioned" off hours.
Also, not having "reactive capacity" might simply mean that your 95th percentile goes from 100ms response time to 300ms. Which again, might be a more cost effective approach.
I think the initial development and ongoing cost of maintaining that reactive capacity is also substantial enough to be considered.
Most of the apps that truly need the elasticity should probably going hybrid anyways. Baseline on dedicated hardware, spikes on spot instances.