<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chaos Engineering on Home</title><link>http://www.bala-krishnan.com/tags/chaos-engineering/</link><description>Recent content in Chaos Engineering on Home</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 23 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://www.bala-krishnan.com/tags/chaos-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Chaos Engineering on a Budget: Running Failure Injection Without a Dedicated Platform</title><link>http://www.bala-krishnan.com/posts/22-chaos-engineering/</link><pubDate>Thu, 23 Jul 2026 00:00:00 +0000</pubDate><guid>http://www.bala-krishnan.com/posts/22-chaos-engineering/</guid><description>There is a version of chaos engineering that gets talked about a lot. Netflix. Chaos Monkey. Dedicated platform teams running sophisticated failure injection frameworks with dashboards and gameday ceremonies and automated rollback. It sounds impressive because it is impressive. It is also not how most teams do it, or need to do it.
Here is how we did it at Salesforce, with a homegrown tool and a spreadsheet.
What we actually built Link to heading The tool itself was not sophisticated.</description></item></channel></rss>