3 ms·
I'm not interested in becoming a cloud practitioner or getting an AWS/GCP/Azure certificate just to host my web app on AWS. All I want to do is just git push m
by colesantiago 4y ago
I'm not interested in becoming a cloud practitioner or getting an AWS/GCP/Azure certificate just to host my web app on AWS.
All I want to do is just git push my code and my app is distributed worldwide in the closest regions, all fast with no deploy scripts or convoluted formation tools.
Heroku and maybe Fly.io are the closest to this goal than other all the other solutions i've tried.
But anything that gets in my way of this goal is friction.
- monero-xmr 4y agoFor small potatoes stuff, yes. For critical business apps that make money and have real customers and jobs on the line, IMO too risky. It isn’t that hard to get to “push code and it deploys” directly with AWS nowadays.
- bradwood 4y agoYou don't need any AWS certs to deploy a few lambdas and a couple of DynamoDB tables. Come on. Your codebase, a few shell scripts, a yaml file for your CI/CD config, and another for your serverless framework definition and you're done -- couldn't be easier.
- moomoo11 4y agoIf it’s that small you could just host from home with a static ip or mapper. If you’re building a commercial product where you’re being paid to provide a service, you’re obviously going to want something robust.
- quickthrower2 4y agoThe other way to protect yourself is to design the app to be easily portable between cloud solutions. A static site can easily move from fly to heroku to vercel to digital ocean. Something written in NodeJS can be moved around those just as easily. Most apps will be naturally portable unless you do something very specfic to your provider. The idea here is not to be "multi cloud" but to say "if this provider goes to shit, give me 2-4 hours, and I can deploy it somewhere else, change the DNS, and then go sip a pina colada".