4 ms·

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 rig

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

theshrike79 4y ago
In the real world you kinda need to pick a provider. Having all your code platform agnostic isn't really a viable option unless you've got budget to spare.
- dghlsakjg 4y ago
  I’m not an infra person by any means, but isn’t that what containers are for?
  - runako 4y ago
    Obviously there are tradeoffs involved in using containers. But aside from that, they also don't typically get you platform independence by themselves unless you also choose not to use any other cloud features (e.g. object storage, queues, IaaS, "serverless" features like DO Functions or Lambdas, key management services, IAM-type services, etc.). 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.
- JohnHaugeland 4y ago
  > Having all your code platform agnostic isn't really a viable option Of course it is
ceejayoz 4y ago
> 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 https://fly.io/launch/heroku ; my Heroku apps are quite portable. https://www.digitalocean.com/community/conceptual_articles/how-to-write-a-serverless-function 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.
jamesfisher 4y ago
This comment is a great example of "What if it changes?" [1] [1]: https://news.ycombinator.com/item?id=31472997 https://news.ycombinator.com/item?id=31472997

theshrike79 4y ago

In the real world you kinda need to pick a provider. Having all your code platform agnostic isn't really a viable option unless you've got budget to spare.

dghlsakjg 4y ago
I’m not an infra person by any means, but isn’t that what containers are for?
- runako 4y ago
  Obviously there are tradeoffs involved in using containers. But aside from that, they also don't typically get you platform independence by themselves unless you also choose not to use any other cloud features (e.g. object storage, queues, IaaS, "serverless" features like DO Functions or Lambdas, key management services, IAM-type services, etc.). 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.
JohnHaugeland 4y ago
> Having all your code platform agnostic isn't really a viable option Of course it is

ceejayoz 4y ago

> 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 https://fly.io/launch/heroku ; my Heroku apps are quite portable. https://www.digitalocean.com/community/conceptual_articles/how-to-write-a-serverless-function 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.

jamesfisher 4y ago

This comment is a great example of "What if it changes?" [1] [1]: https://news.ycombinator.com/item?id=31472997 https://news.ycombinator.com/item?id=31472997