Resiliency and production readiness have come sharply into focus in the last decade as key areas of technical investment to enable organizations to build trust with their customers and scale/deliver innovation rapidly. The criticality of verifying cloud readiness of code prior to deploy as well as conducting resiliency experiments in cloud-native application ecosystems has resulted in Resiliency becoming a key strategy in many engineering team playbooks. Drawing from my previous experiences with Chaos Engineering at Netflix and Walmart, this talk will focus on how any team can begin investing iteratively in reliability and observability and build a "Minimum Viable Resiliency" plan.

In this talk, we will discuss setup, running and planning stages of a Chaos/Resilience testing discipline as a means to achieving the "Minimum Viable Resiliency". Using learnings from the industry, we will list out ways to plan small incremental changes in production readiness and KPIs to measure improvement. These steps will help engineering teams of all sizes to get more confidence in their software delivery and delight their customer base. 

Keeping Development teams motivated and productive has always been a challenge even in a pre-pandemic office work environment. In the new Remote-first work reality, these challenges bring new tradeoffs between Developer joy and releasing new features quickly and maintaining a high bar on quality. Add to this the hurdles in communication and this presents a potential obstacle for most businesses and their bottom line. But using gamification exercises, quality gating, guardrails and modified KPIs combined with a reward/objective-based system for distributed development teams can bring in a new way to drive developer effectiveness in teams. Combining learnings from running remote distributed teams for over a decade (as well as through the pandemic) this talk will focus on the wins/learnings/opportunities that can be a blueprint for enabling happy dev teams that deliver consistent quality at high velocity

This talk will focus on Walmart’s home-grown open sourced solution for all workflow orchestration needs - "Concord". We will discuss the extremely rewarding continuous deployment journey that we undertook at Walmart that led us down the path of creating Concord. We will dissect some key successful case studies that Concord helped us solve at Walmart scale. In addition, we will talk about the various challenges we faced and continue to face during our journey and how the fast-changing industry landscape (with respect to continuous delivery of software) influences our growth inside Walmart.

You will be able to understand:

• How we deal with challenges at Walmart scale
• Why we chose to open source our solution
• How we enable a complete CD cycle using Concord
• How Concord empowers deployments in a hybrid cloud model

The practice of Chaos Engineering has established the importance of running resiliency experiments in cloud-native application ecosystems. As the field of Chaos/Resilience Engineering has matured and attained widespread adoption, a need has emerged for engineering organizations to quantify the costs of running such a program. Additionally, sustained investment in any long-running program will require metrics (KPIs) to show effectiveness to Executive Leadership.

In this talk, we will discuss the setup, running and maintenance stages of a high performing Chaos/Resilience engineering program irrespective of the size of the organization. We will analyze the key metrics that should be tracked along with the optimum cadence of chaos exercises. Also, with the rapid advancement of CI/CD tools and cloud deployment technologies, we look at enhancing the impact of chaos engineering by deep integration into the continuous deployment pipeline.