My short hot take on DevOps and infrastructure as code: "Infrastructure as code has it backwards" ------- Take the development of programming as an analogy:

My short hot take on DevOps and infrastructure as code: "Infrastructure as code has it backwards" ------- Take the development of programming as an analogy: * Punched cards * Programming in assembler * Goto * Callable procedures * Proper functions * Compiled languages (There used to be companies just selling a big C compiler) * Interpreters/JIT compilation/... * ... ------- And here's a similar progression: * Servers in your basement * Some server rented where you login via SSH * Docker/Kubernetes/Clusters in the cloud * Lambdas and other serverless solutions * ... As a sibling comment pointed out: We're still in the stone ages. Somewhere between punch cards and proper functions. ------- To rephrase it in reversal: "Infrastructure as code has it backwards" Right now, we manually partition our code, then provision infrastructure and then push our code to this infrastructure. Instead, we should take a high level language that compiles to the cloud: Just write your business logic and the the compiler figures out what clusters/services/event-buses/databases/etc to use; It will automatically partition the code, package, build, provision, push, update. And there's even room for something like JIT: Based on the load parts of your logic get, the compiler could switch databases. Also: Automated data migrations based on your code updates. But I guess we'll end up with a big distributed virtual machine that scales infinitely and completely hides the existence of servers. There's already some glimpses of this future: No-code, the magic pulumi does with lambdas, several language projects that get rid of the file system and just store the AST in a DB, smart contracts where you pay for single computation steps... ------- But back to the question: Kubernetes/AWS/etc is a lot of work because it's not really THE SOLUTION.