Register or log in to access this video
In established ecosystems, “Chaos Engineering” is a simulation. In Nigeria, it is a daily reality. Learn the “Zero-Trust” patterns and leadership strategies we use to build bulletproof systems when the infrastructure is constantly failing us.
In established ecosystems, engineering leaders obsess over “Chaos Monkey”, software designed to randomly crash servers to test resilience. In Abuja Nigeria, we don’t need Chaos Monkey. We operate on a national power grid that collapsed over 20 times in the last two years, amidst hundreds of fiber cuts and network disruptions.
For my team, failure isn’t a theoretical risk to be simulated; it is the default state of our existence.
This session explores the unique engineering discipline required to build world-class products in a “low-trust” infrastructure environment. I will share the war story of a Black Friday launch for our high-volume fintech platform where we faced the “Perfect Storm”: a major fiber cut took our office offline, our primary payment partner suffered a latency spike, and the power grid collapsed, all within an hour.
Most teams would have folded. Mine didn’t even pause.
I will detail the “Zero-Trust” framework that allowed us to survive, and how you can apply it to your own stack:
- The Architecture of Distrust: How we moved from synchronous coupling to an aggressive asynchronous model. We assume every external API (Stripe, Twilio, AWS) will fail 50% of the time. I will show how we used Redis-backed persistent queues and the Outbox Pattern to allow our app to “hold its breath” for hours without crashing.
- The “Air-Gapped” Developer: How we built “Offline-First” dev environments. By dockerizing our entire stack locally (including mocked third-party services), we empowered engineers to ship code even while tethered to 3G mobile hotspots, a lesson in eliminating cloud dependencies that speeds up any team.
- Leading Through “Outage Fatigue”: Constant firefighting burns out engineers. I will share my playbook for psychological safety, shifting the culture from “Who broke it?” to “How did the system absorb the shock?”
Attendees will leave with a new perspective: You don’t need to be in Africa to face failure. By applying these “survivalist” constraints, you can build systems that are bulletproof anywhere.
Key takeaways
- Organic Chaos Engineering: Why “simulated” failure pales in comparison to real-world constraints, and how to audit your system for “happy path” bias.
- Asynchronous by Default: Implementing specific patterns (Circuit Breakers, Leaky Buckets, Outbox) to decouple uptime from third-party dependencies.
- Psychological Safety in a Firefight: A manager’s guide to preventing burnout when the environment is constantly fighting against you.
