Yes you can, but it’s very difficult and not worth the effort IMO.
The first problem is that you wind up using the least common denominator. You’re paying public cloud providers a premium, so this essentially equates to throwing away money.
The second is that there are some cases where what seems like the same thing isn’t, or best practice is wildly different between providers. Get in a room with an AWS expert and an Azure expert and talk about what an account is.
Re:Unbundling AWS
by adrianmonk on Sunday December 01, 2019 @03:45PM
(#21677689)
You raise a good point. Upon re-reading, portability to a different cloud is probably not the point. It's more likely about being on the cloud you're already one but having the choice to take only parts of the platform, instead of taking Amazon everything at every layer of the stack. So you're still on Amazon or whoever's cloud, but you may not use (for example) their database if you like some other database.
In other words, it's not about moving your entire stack off Amazon's cloud, it's about moving parts of your stack off Amazon's software even if all of it may still run inside Amazon's cloud.
Couldn't you build your software stack in a cloud-portable way but, at any given time, still have 100% of it on whatever your current cloud provider is? And then switch to another cloud provider from time to time if/when the costs make it worthwhile.