DevOps & Continuous Delivery sessions

With systems like Travis CI, Circle CI, and CodeBuild, we're never more than a few lines of YAML away from a complete continuous delivery pipeline. However, ephemeral build systems constantly recreate the world from scratch, increasing build time and lengthening the CD feedback loop. John Chapin addresses those challenges and shares a reference pipeline using AWS CodePipeline and CodeBuild. Read more.

Serverless architecture opens up a world of opportunity for development, providing ease of use while deploying and operating at scale. But this can decrease visibility, making it difficult to see when your environment is misbehaving in terms of throughput, functionality, and performance. Tal Weiss introduces a successful new framework for debugging serverless architecture with real-world examples. Read more.

When developers start as tech leads or architects, they're often confused about how and where to start. Stefania Stefansdottir walks you through tasks and examples of how to get a team up and running with a new project in an existing ecosystem as well as pitfalls and gotchas to keep in mind. Read more.

Mandy Waite shares how she and her team at Google Cloud are working to make developers happier and more productive and details how her team uses their internal research and expands upon it to collaborate with Google Cloud partners and open source projects. Join in to get tips on how to cultivate a DevOps culture inside your company. Read more.

Being wrong is often seen as the worst thing that can happen, especially when you build business-critical applications and services. Never before has software owners had such an opportunity, or the power, to be wrong. Russ Miles turns being wrong into a superpower for you and your organization. Read more.

A loosely coupled software architecture and an organizational structure to match is one of the biggest predictors of continuous delivery performance. Nick Tune explains why technical leaders must adopt a sociotechnical mindset to minimize dependencies and maximize team autonomy, optimizing end-to-end value creation and delivery speed. Read more.

How can architects collect and make sense of stories from the tactical frontlines to inform long-term technology strategy and vision? Cat Swetel reviews published time span research and works through what the shorter time spans of Agile and CI/CD may mean for software architecture and sociotechnical systems overall. Read more.

Credit card fraudsters are always changing their behavior and developing new tactics. For banks, the damage isn’t just financial; their reputations are on the line. So how do they stay ahead of the crooks? Sarah LeBlanc and Hany Elemary explore a system that utilizes continuous delivery for machine learning to allow for rapid experimentation and the deployment of models to catch these fraudsters. Read more.

There are two common architectural failure modes: hierarchical command and control from ivory-tower architects with strict approvals and rigorous control gates, and chaos with every team doing what they want with little governance. Jonny LeRoy explores the Goldilocks zone that ensures that teams handle organizational risks and opportunities while giving themselves as much autonomy as possible. Read more.

A free puppy is great but also takes a lot of time, energy, and money. Likewise, when we make a build-versus-buy calculation, it's easy to miss several important parts of the calculation, including maintenance, updating, security, availability, and finding operators. None of those are easy to articulate or value for either side. Join Heidi Waterhouse to learn why business value is more than money. Read more.

Most organizations want faster, more-incremental delivery of their applications, but fragile tests and complex continuous delivery pipelines often make this difficult. What if the problem isn’t the pipeline but the architecture of the system? Ken Mugrage details the architectural choices that will help you enable stable tests and faster pipelines. Read more.