DevOps at scale requires predictability and consistency. Your application code is versioned. Infrastructure-as-code defines your environments. But what about the process?
How do you define your processes as code? What are some use cases and best-practices for ensuring your automation is versionable, testable, and repeatable.
Watch the Replay of the Episode
This episode features:
Technical Evangelist (with a hard ‘g’) for Apcera. USENIX board member. Talkin’ about System Administration/DevOps/SRE, Perl, and stuff.
Author of “Continuous Delivery Pipeline – Where Does It Choke?“.
J. Paul Reed
J. Paul Reed has over 15 years experience in the trenches as a build/release engineer, working with such companies as VMware, Mozilla, Symantec, and Salesforce. He speaks internationally on release engineering, DevOps, operational complexity, and human factors.
Mark is learning how to make himself dispensable with automation and continuous data…
Cloud Specialist. Author of Amazon Web Services in Action. Software Engineer, Speaker, Teacher and Consultant.
On the Next Episode of Continuous Discussions:
Episode 49: Deployment Patterns
Join us on September 6, to discuss best practices for advanced deployment patterns and deployment pipelines.
This episode will feature:
Snake, Gopher & Whale handler. Frequent Flyer. Automates all the things. Continuous Delivery Evangelist.
DevOps and Agile Consultant at MattAgile.com
Sr. Engineer at Datawire.io. Phil has extensive experience building and operating distributed systems and continuous delivery pipelines in both the Internet of Things and web services spaces.
Continuous Discussions (#c9d9) podcasts air every other Tuesday. See all episodes here.