With AWS especially there is a shitton of proprietary stuff. Most of the friction is in knowledge however; the cloud environments differ, are configured differently, have different limitations and caveats, etc. Someone who has only ever worked with AWS will have to learn a lot of things anew if they switch. Hell there’s a reason why “AWS engineer” is a dedicated role in some companies.
Now, if you only manually set up some VMs and configure them like you would a regular server then sure, it’s easy to migrate. But when you are missing 99% of the features of the cloud environment are you actually using it?
For me the purpose of the cloud is the ability to deploy my projects on rented infrastructure independently of the provider. Tools like Terraform and Kubernetes help with the abstraction of providers.
As for proprietary features I prefer to use open source alternatives like Supabase, which I then can deploy to any cloud and migrate between clouds if needed.
Well then you aren’t probably taking advantage of most of the stuff AWS offers and is actually really good for. Which isn’t really criticism, but then I wouldn’t really call it cloud? It’s more like just infrastructure as a service.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
Follow the programming.dev instance rules
Keep content related to programming in some way
If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos
With AWS especially there is a shitton of proprietary stuff. Most of the friction is in knowledge however; the cloud environments differ, are configured differently, have different limitations and caveats, etc. Someone who has only ever worked with AWS will have to learn a lot of things anew if they switch. Hell there’s a reason why “AWS engineer” is a dedicated role in some companies.
Now, if you only manually set up some VMs and configure them like you would a regular server then sure, it’s easy to migrate. But when you are missing 99% of the features of the cloud environment are you actually using it?
For me the purpose of the cloud is the ability to deploy my projects on rented infrastructure independently of the provider. Tools like Terraform and Kubernetes help with the abstraction of providers.
As for proprietary features I prefer to use open source alternatives like Supabase, which I then can deploy to any cloud and migrate between clouds if needed.
Well then you aren’t probably taking advantage of most of the stuff AWS offers and is actually really good for. Which isn’t really criticism, but then I wouldn’t really call it cloud? It’s more like just infrastructure as a service.
Infrastructure as a service is literally the definition of a cloud. Everything is just bells and whistles.