

During the entire article I kept thinking how it wasn’t best practice to use the same cloud for everything, that you needed a different cloud because occasionally, your account can just get nuked from orbit. People dont understand that these corporations are really just held together with luck prayers and duct tape. Software enables us to develop in the worst ways possible, and then call it production.
This is a really interesting read, but this dude missed a major component of best practices, which is that your architecture needs to be able to respond to a proper disaster, which includes Amazon just dropping out of the sky and nuking your entire account.
Frankly, it’s shocking that he didn’t have local copies or a home server that he kept backups too. I’ve seen some people mention that a multi-cloud architecture is hard to set up, which is true, it’s also expensive, but I don’t think it would be super hard to set up, like, a blob storage in Azure, or a Google Cloud Storage, to just keep backups of whatever you’re working on. We should always keep in mind that our accounts getting locked is always a possibility.
It’s kinda weird, normally when you hear about things like this, it’s the other way around where somebody was running a major production component on personal infrastructure and couldn’t handle the bare metal.