The Stack Overflow Podcast25 Tammi 2023

How chaos engineering preps developers for the ultimate game day

In complex service-oriented architectures, failure can happen in individual servers and containers, then cascade through your system. Good engineering takes into account possible failures. But how do you test whether a solution actually mitigates failures without risking the ire of your customers? That’s where chaos engineering comes in, injecting failures and uncertainty into complex systems so your team can see where your architecture breaks.

On this sponsored episode, our fourth in the series with Intuit, Ben and Ryan chat with Deepthi Panthula, Senior Product Manager, and Shan Anwar, Principal Software Engineer, both of Intuit about how use self-serve chaos engineering tools to control the blast radius of failures, how game day tests and drills keep their systems resilient, and how their investment in open-source software powers their program.

Episode notes:

Sometimes old practices work in new environments. The Intuit team uses Failure Mode Effect Analysis, (FMEA), a procedure developed by the US military in 1949, to ensure that their developers understand possible points of failure before code makes it to production.

The team uses Litmus Chaos to inject failures into their Kubernetes-based system and power their chaos engineering efforts. It’s open source and maintained by Intuit and others.

If you’ve been following this series, you’d know that Intuit is a big fan of open-source software. Special shout out to Argo Workflow, which makes their compute-intensive Kubernetes jobs work much smoother.

Connect on LinkedIn with Deepthi Panthula and Zeeshan (Shan) Anwar.

If you want to see what Stack Overflow users are saying about chaos engineering, check out

Chaos engineering best practice

, asked by

User NingLee

two years ago.

See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Tämä jakso on lisätty Podme-palveluun avoimen RSS-syötteen kautta eikä se ole Podmen omaa tuotantoa. Siksi jakso saattaa sisältää mainontaa.

Jaksot(983)

AI, JD, and other letters of the law

Ryan chats with Kevin Frazier, director of the AI Innovation and Law program at the University of Texas School of Law, about the legal and social impacts of data centers, the realities of workforce di...

15 Syys 38min

AI cybersecurity is a cat and mouse game

Ryan chats with Sam Curry, CSO at Zscaler, about where human intelligence sits in the new security landscape with AI, why shifting security protections closer to applications helps limit probes for vu...

11 Syys 27min

Java’s age is its AI superpower

SPONSORED BY IBMRyan welcomes Markus Eisele to the program to talk about why your coding agent should be writing Java. They talk about why the long history of Java both makes for a stable language and...

9 Syys 35min

Scaling your money safely with AI

Episode notes: This episode with Paypal’s CTO Srini Venkatesan was recorded at the Ai4 conference. Listen to our other Ai4 conversation with Greg Jennings, VP of Engineering for AI Products at Anacond...

8 Syys 28min

How to build a secure-by-default AI coding agent

Ryan chats with Greg Jennings, VP of Engineering for AI Products at Anaconda, about what it takes to build a secure-by-default AI coding agent, why prompts shouldn't be treated as strict security guar...

4 Syys 32min

The good ol’ days of building Java

Ryan sits down with Tim Lindholm, an early contributor to the Java language at Sun Microsystems, to chat about what it was like building one of the most popular programming languages ever at its incep...

1 Syys 30min

When you keep AI Lean, you keep AI correct

Ryan chats with Leo de Moura, Senior Principal Applied Scientist at AWS and the creator of the Lean language, about proving correctness in AI agents with the Lean language, how automated reasoning com...

28 Elo 25min

Inside LinkedIn's cognitive memory agent for agentic personalization

Ryan is joined by Praveen Bodigutla, Principal AI Researcher at LinkedIn, to chat about the four-layer memory system his team built to give LinkedIn's hiring assistant a persistent, personalized state...

25 Elo 32min