Several patterns emerged out of cloud services that enable cloud services to work better - namely event driven architectures, various cost savings strategies, HA/DR postures, etc - that cannot be applied to non-cloud architectures or even monoliths. If your team wants these patterns, you need to go cloud. Said differently: if they want experience in AWS, that's a proxy for wanting to learn these other techniques.<p>Moreover, this tweet is the rant of a single person that apparently doesn't care for AWS.
totally agree (make that N=2). Almost nothing can be trusted anymore to an engineering team that will not result in it being implemented AWS/Azure/etc. More than ever we have incredible processors, loads of memory and storage and bandwidth, that allow us to do insane stuff within the confines of a single machine, but no! we want to go serverless everthing.<p>For many, many applications than can be deployed on a single server, AWS introduces the potential of uncontrollable lifetime costs, more threat vectors, vastly increased vendor lockin, lower performance....<p>AWS and their ilk are like cults now. Okay! need to stop