> just making up scenarios where you need to scale to 100x isn't actually engineering. Even for "peak" Amazon's concern seemed limited to about ~5x daily TPS m

> just making up scenarios where you need to scale to 100x isn't actually engineering. Even for "peak" Amazon's concern seemed limited to about ~5x daily TPS maximums unless one had extraordinary evidence. The counter-balance to limiting resource balooning to 5x scale is introducing Erlang-B modelling. Depending on how many 9s you require, you may need way more service availability than expected. The 100x calculations are probably doubly wrong (both too large and too small), providing negative value false confidence.