I don’t mean to sound flippant here but going Serverless would obviate the need for much of this guide.
An engineer’s guide to cloud capacity planning
11–20 of 36 posts
Re: An engineer’s guide to cloud capacity planning
#12If you are a small startup and do not have strict regulatory or other special req. run on something simple like DO, Vultr etc. and save yourself pain and $.
How do you work on Digital Ocean or some other cloud without VPC? I haven't been able to figure this out. Sure, if I just have 1 or maybe 2 servers it's fine. More than that what are you doing? Mesh networking like ZeroTier? iptables on every machine? It just seems like a lot more work than setting up a VPC.
Re: An engineer’s guide to cloud capacity planning
#13I don’t mean to sound flippant here but going Serverless would obviate the need for much of this guide.
Going serverless would increase your costs significantly. Have you seen how much AWS charges for Lambda use? Where did this myth of serverless saving you money come from?
Re: An engineer’s guide to cloud capacity planning
#14I don’t mean to sound flippant here but going Serverless would obviate the need for much of this guide.
I think that you still need capacity planning for "serverless" architectures as well. You need to forecast growth of usage and costs for accounting and budgeting purposes. Does your serverless usage scale linearly with new customers? Or new widgets on the platform? Great, if we're planning on adding 10,000 widgets to the platform next quarter how much will our serverless bill go up? We still need to think about these things.
Also, and this may be my lack of experience, there seems to still be a big requirement for more traditional cloud hosting for databases in a serverless architecture. You have to store that state somewhere.
Re: An engineer’s guide to cloud capacity planning
#15If you are a small startup and do not have strict regulatory or other special req. run on something simple like DO, Vultr etc. and save yourself pain and $.
How do you work on Digital Ocean or some other cloud without VPC? I haven't been able to figure this out. Sure, if I just have 1 or maybe 2 servers it's fine. More than that what are you doing? Mesh networking like ZeroTier? iptables on every machine? It just seems like a lot more work than setting up a VPC.
Not to say it's as robust a strategy as a VPC, but DO does have something called a cloud firewall. It supports the idea of tags that apply to groups of servers.
https://www.digitalocean.com/community/tutorials/an-introduc...
Re: An engineer’s guide to cloud capacity planning
#16If you are a small startup and do not have strict regulatory or other special req. run on something simple like DO, Vultr etc. and save yourself pain and $.
How do you work on Digital Ocean or some other cloud without VPC? I haven't been able to figure this out. Sure, if I just have 1 or maybe 2 servers it's fine. More than that what are you doing? Mesh networking like ZeroTier? iptables on every machine? It just seems like a lot more work than setting up a VPC.
A VPN can work very well. tinc [1] for example. Easy to deploy, sustains Gigabit speeds even on weak VMs. And works across different providers.
Re: An engineer’s guide to cloud capacity planning
#17Earlier quoted context omitted.
How do you work on Digital Ocean or some other cloud without VPC? I haven't been able to figure this out. Sure, if I just have 1 or maybe 2 servers it's fine. More than that what are you doing? Mesh networking like ZeroTier? iptables on every machine? It just seems like a lot more work than setting up a VPC.
A VPN can work very well. tinc [1] for example. Easy to deploy, sustains Gigabit speeds even on weak VMs. And works across different providers. [1] http://tinc-vpn.org
And is about as good as building network on GRE tunnel, because its
homebrew cryptography is written by a dilettante.
Re: An engineer’s guide to cloud capacity planning
#18If you are a small startup and do not have strict regulatory or other special req. run on something simple like DO, Vultr etc. and save yourself pain and $.
How do you work on Digital Ocean or some other cloud without VPC? I haven't been able to figure this out. Sure, if I just have 1 or maybe 2 servers it's fine. More than that what are you doing? Mesh networking like ZeroTier? iptables on every machine? It just seems like a lot more work than setting up a VPC.
if you are running simple web app not having VPC is not a big issue.
Re: An engineer’s guide to cloud capacity planning
#19I don’t mean to sound flippant here but going Serverless would obviate the need for much of this guide.
Going serverless would increase your costs significantly. Have you seen how much AWS charges for Lambda use? Where did this myth of serverless saving you money come from?
Under-utilized machines in people's stack.
Re: An engineer’s guide to cloud capacity planning
#20> 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.
It's not coincidental; I believe the 'sole application' the author talks about was in fact an online game.