IN PERSON!! Infrastructure Code Design Patterns

Infrastructure as a House

For the past ten years, we've been focusing on the "as code" part of "infrastructure as code", making sure we're applying the best software development practices to our infrastructure code. But what if that's not the best idea?

Let's spend some time examining exactly how infrastructure code relates to product code, what the similarities are, and (more interesting) what the differences are. From there, we can start to discuss what design patterns from product code do apply to infrastructure code, and discuss some infrastructure code practices that would be unheard of when developing and deploying product code.

This talk will give you some practices you can apply tomorrow and start improving how you develop infrastructure code, as well as talk about different architectural approaches to take when building and maintaining your software infrastructure.

Bio
jonny sywulak has been developing software long enough that he stopped saying the actual years since it makes him feel old, helping delivery teams reduce cycle time and increase quality of their products. He's worked with both enterprise corporations and government agencies to achieve success moving their applications in the cloud and building a strong devops culture. He's currently based in Philadelphia and has strong opinions about both soft-pretzels and soft-ware deployment frequency, either of which he'll talk your ear off about with very little prompting. He also uses way too many emojis in his commit messages. 🫠