PurePerformance 058 The State of CI, CD & Observability: Why you don’t have to build it yourself
Mar 26, 2018
43:43
You wouldn’t build your own Jenkins – would you? Neither would you build your own CRM, Office or Email service. So why are the “cool” DevOps kids still building their own continuous delivery scripts, log analytics and monitoring and showing it off on GitHub or conferences?
In this episode we invited Steve Burton (@BurtonSays), CD geek at harness.io, and discussed the current state of Continuous Delivery and the role of Observability (that’s Monitoring++). We learn about use cases that commercial vendors in these spaces provide out-of-the-box, the APIs they offer to integrate these tools into a larger eco-system and why we believe it’s time to stop building your own tools but investing in building better software for your users. We also learn about Blue/Green deployments, Canary Releases, Continuous Verification and Rollback vs Roll-forward.
In this episode we invited Steve Burton (@BurtonSays), CD geek at harness.io, and discussed the current state of Continuous Delivery and the role of Observability (that’s Monitoring++). We learn about use cases that commercial vendors in these spaces provide out-of-the-box, the APIs they offer to integrate these tools into a larger eco-system and why we believe it’s time to stop building your own tools but investing in building better software for your users. We also learn about Blue/Green deployments, Canary Releases, Continuous Verification and Rollback vs Roll-forward.