Why would anyone tie themselves to digital ocean
Single infrastructure code dies and the author can't usually save it
Ask a heroku fan how they're feeling right now before moving forward with any single host approach
Single infrastructure code dies and the author can't usually save it
Ask a heroku fan how they're feeling right now before moving forward with any single host approach
Just fine? Fly.io has a fairly seamless automated migration at https://fly.io/launch/heroku ; my Heroku apps are quite portable.
https://www.digitalocean.com/community/conceptual_articles/h... shows a pretty similar approach to Lambda - they just invoke a function with a handler. You could run the same handler on AWS Lambda or Cloudfront's workers, probably without any changes.
Having all your code platform agnostic isn't really a viable option unless you've got budget to spare.
In my experience, it's building for the cloud as a platform vs targeting a pre-cloud infra that ties you to a particular cloud. You can obviously DIY all of that in your own containers, but then you're making a choice to invest in infra instead of buying it.
Of course it is