An engineer’s guide to cloud capacity planning
increment.com
An engineer’s guide to cloud capacity planning
1–10 of 36 posts
Re: An engineer’s guide to cloud capacity planning
#2I was hoping for some insight when you're hosting your own private cloud, that seems quite a bit more tricky. It's easy to prepare to scale up/down your deployment when all the hardware is already there, but when you're the one running the actual cloud and need to do the same, you can't just do an API call and suddenly have another 100 U of servers and switches racked, cabled and provisioned.
Still a nice article though!
Re: An engineer’s guide to cloud capacity planning
#3I think we found the Pokemon Go engineering team.
Re: An engineer’s guide to cloud capacity planning
#4This seems more about capacity planning your application when running in the cloud. I was hoping for some insight when you're hosting your own private cloud, that seems quite a bit more tricky. It's easy to prepare to scale up/down your deployment when all the hardware is already there, but when you're the one running the actual cloud and need to do the same, you can't just do an API call and suddenly have another 10…
I am not associated with either of these companies in anyway other than looking for a solution to the same problem you mentioned.
Re: An engineer’s guide to cloud capacity planning
#5> Perhaps surprisingly for engineers who work in mission-critical business applications, occasional spikes of 90%+ of our users being entirely unable to use the sole application of our company was an entirely acceptable engineering tradeoff versus sizing our capacity against our peak loads. I think we found the Pokemon Go engineering team.
That paragraph reads to me “screw the users!” - and for them to say that around “mission critical” seems they don’t understand the critical mission...
Re: An engineer’s guide to cloud capacity planning
#6Re: An engineer’s guide to cloud capacity planning
#7> Perhaps surprisingly for engineers who work in mission-critical business applications, occasional spikes of 90%+ of our users being entirely unable to use the sole application of our company was an entirely acceptable engineering tradeoff versus sizing our capacity against our peak loads. I think we found the Pokemon Go engineering team.
Acceptable engineering trade off and acceptable business decision trade off are not always the same thing. That paragraph reads to me “screw the users!” - and for them to say that around “mission critical” seems they don’t understand the critical mission...
The business constraints often include cost. They also may be arbitrarily far from 100% uptime.
Re: An engineer’s guide to cloud capacity planning
#8Earlier quoted context omitted.
Acceptable engineering trade off and acceptable business decision trade off are not always the same thing. That paragraph reads to me “screw the users!” - and for them to say that around “mission critical” seems they don’t understand the critical mission...
The critical mission is to deliver as much business functionality as possible within the business constraints. The business constraints often include cost. They also may be arbitrarily far from 100% uptime.
Re: An engineer’s guide to cloud capacity planning
#9This seems more about capacity planning your application when running in the cloud. I was hoping for some insight when you're hosting your own private cloud, that seems quite a bit more tricky. It's easy to prepare to scale up/down your deployment when all the hardware is already there, but when you're the one running the actual cloud and need to do the same, you can't just do an API call and suddenly have another 10…