At this year’s swamUP 2020 conference, we were fortunate to have several customers who showcased their skillful use of our products for achieving ambitious goals. One such session presentation was delivered by Navin Ramineni, Director of Infrastructure Engineering at Salesforce.
Most modern software today has moved aggressively into using third-party open source dependencies to reduce duplication and accelerate development by using pre-existing code.
Developers are building and deploying to production with greater frequency. Elite organizations are deploying to production multiple times per day. All the while we continue to distribute our applications even wider with the adoption of micro-services, and global deployments. This consistent churn and increasing code complexity create the perfect storm that makes finding problems even harder. How do you know the changes just committed actually deployed? How do you know the changes worked?
Long release cycles are no longer viable in the world of software development. The promise of DevOps has been to materially shrink time to value. Like most meaningful transitions, this one hasn’t always been a simple flip of a switch. For many organizations, development teams have become complex and unwieldy. So, the custodians of DevOps have found it difficult to achieve broader adoption of DevOps principles across engineering teams.