Well-Oiled DevOps Rides on Immutable Infrastructure


Manage episode 256254646 series 75006
By The New Stack Makers and The New Stack. Discovered by Player FM and our community — copyright is owned by the publisher, not Player FM, and audio is streamed directly from their servers. Hit the Subscribe button to track updates in Player FM, or paste the feed URL into other podcast apps.
To hear more podcasts listen here: https://thenewstack.io/podcasts/ Prisma, from Palo Alto Networks, sponsored this podcast, following its Cloud Native Security Live, 2020 Virtual Summit held Feb. 11, 2020. The adoption of “immutable infrastructure” has emerged as a viable way to improve DevOps processes and culture. By introducing more of a standardization in application deployment and management, immutable infrastructure helps, among other things, to foster a better collaborative environment among developers, operations, security team and other stakeholders. “Immutable infrastructure gives you the ability to have a consistent environment, across your entire fleet of systems, which gives you a simpler and more predictable deployment,” Mike Liedike, manager, Deloitte Consulting’s Innovations and Platforms team, said. “It allows you to do the testing more consistently and promote your environments from development to test to prod.” In other words, the adoption of immutable infrastructure is often a hallmark of a highly functional DevOps. In this edition of The New Stack Makers podcast recorded live at Palo Alto Networks’ studio in Santa Clara, CA, Liedike offers further insight and analysis of what the adoption of an immutable infrastructure can mean for your organization. A good starting point to describe how immutable infrastructure works is by first detailing how it does not work — or more specifically, what “mutable” infrastructure is and how it differs compared to immutable infrastructure. Using the example of Apache servers, Liedike noted how admins might upgrade the servers by installing the latest version of the Web server software with configuration-management tools. The problem, Liedike said, is that “across 1,000 instances, you have a lot of room for error and inconsistency.” “With immutable infrastructure, instead of doing those changes in place, you would actually build a new server, with all the upgrades already in place, and then deploy your systems and decommission the old ones,” Liedike said. Sponsor Note

788 episodes