4 ms·
Moving from AWS to DO will force you to handle a lot more devops/IT stuff to work around network and api reliability issues. So to make that worth it, it'd real
by 23david 11y ago
Moving from AWS to DO will force you to handle a lot more devops/IT stuff to work around network and api reliability issues. So to make that worth it, it'd really depend on how much money you are looking to save and on the IT/devops resources you have available.
AWS may be more expensive, but perhaps instead of migrating away from AWS to another provider, you can start using AWS more efficiently. Most people I've helped out in similar situations were able to reduce their AWS bills between 50-75%.
- davismwfl 11y agoThis is one of my concerns. We have spent years becoming AWS "experts" and while I want to save money, I also feel really comfortable with Amazon and their offers. We don't use a lot of custom solutions from AWS and are not heavily invested in devops peeps, so the dev staff serve both needs. I can't say our bill from AWS is horrible, but I have challenged our team to reduce costs to try and make our process more cost effective so I can hire 1-2 more people. DO came up as an option. Not that we are spending that much with Amazon alone but that it may be an option to help save some money. To be totally honest, AWS has been so awesome to us it is hard for me to imagine leaving them, but I can't be blind to saving some cash. Thanks for the opinion and option.
- 23david 11y agoBased on what you've said about your current situation, I definitely think that you'd be better off staying on AWS. Have you looked into using reserved instances?
- davismwfl 11y agoWe had some before, and will likely stay and do some more RI's. AWS has been awesome to us, but I didn't want to ignore other options if they could save us money and provide the same reliability and capabilities. Thanks for the input.