<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Resilience-Testing on Pi Stack</title><link>https://www.pistack.xyz/tags/resilience-testing/</link><description>Recent content in Resilience-Testing on Pi Stack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 20 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.pistack.xyz/tags/resilience-testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Toxiproxy vs Pumba vs Chaos Monkey: Self-Hosted Fault Injection Guide 2026</title><link>https://www.pistack.xyz/posts/2026-04-20-toxiproxy-vs-pumba-vs-chaosmonkey-self-hosted-fault-injection-chaos-testing-guide-2026/</link><pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/2026-04-20-toxiproxy-vs-pumba-vs-chaosmonkey-self-hosted-fault-injection-chaos-testing-guide-2026/</guid><description>&lt;p>Building resilient distributed systems requires more than unit tests and load tests. You need to verify your applications survive real-world failures: network latency, dropped packets, service crashes, and infrastructure outages. Fault injection tools let you deliberately break things in staging environments so your production systems can handle failures gracefully.&lt;/p></description></item></channel></rss>