The Current State of Infrastructure From Code

This post has been a long time coming. Back in September, I teased about <a href="https://betterprogramming.pub/my-first-impressions-of-infrastructure-as-code-13c44bdc7743" rel="noopener ugc nofollow" target="_blank">my first impressions of Infrastructure from Code (IfC)</a>. Around that time I began an experiment. I wanted to see how people were approaching the Infrastructure from code problems. Infrastructure from Code is a relatively new way to build out your cloud architecture. A framework will take your code and convert it to cloud resources for you. This omits the declarative part of serverless development (or cloud development in general) which ultimately lets you move faster. Focusing on your business logic instead of building SAM templates or CDK constructs really lets you hone in on actually solving your business problem. Taking out the infrastructure decisions when building in the cloud is an interesting thought that not everyone is going to appreciate. Some people will fight tooth and nail to keep a sense of control over what gets pushed into their environments. But as <a href="https://twitter.com/jeremy_daly" rel="noopener ugc nofollow" target="_blank">Jeremy Daly</a> says, <a href="https://www.jeremydaly.com/cloud-native-versus-native-cloud-apps/" rel="noopener ugc nofollow" target="_blank">control is an illusion</a>. The desire to control your infrastructure really boils down to the desire to optimize (usually). In the future, <a href="https://betterprogramming.pub/the-future-of-serverless-1c945a75f4be" rel="noopener ugc nofollow" target="_blank">that might be handled for us too</a>! Putting aside the future for a second, I want to talk about what’s available now. Let’s take a look at what you can explore today to start getting your infrastructure managed for you. <a href="https://betterprogramming.pub/the-current-state-of-infrastructure-from-code-cbd3469ecdc5">Website</a>