rum-and-code / mutineer

What is mutineer?

Mutineer brings chaos engineering to Elixir, inspired by Netflix's Chaos Monkey, by letting you wrap functions to inject random failures like errors, exceptions, timeouts, nil returns, or process exits at tunable rates. It helps build confidence in system behavior through experiments, simulating real-world disruptions without Kubernetes-specific setup. Disabled by default with minimal overhead, it's a lightweight chaos engineering tool for testing resiliency in Phoenix apps or distributed systems.

Why is it gaining traction?

In an Elixir world short on native chaos engineering tools—unlike the crowded GitHub chaos monkey scene for other languages—Mutineer stands out with dead-simple attribute decorators or macro wrappers for functions, plus flexible failure types and global config toggles. Developers hook on its zero-config safety and runtime disable, making chaos engineering tests painless in dev/staging without prod risks. Low overhead means it slots into existing codebases effortlessly.

Who should use this?

Elixir backend engineers hardening Phoenix services against failures, or ops teams running chaos engineering tests on OTP apps before staging deploys. Ideal for devs writing resilient GenServers or API handlers who want quick error-injection experiments, not full Kubernetes chaos frameworks.

Verdict

Worth a spin for Elixir chaos engineering experiments if you're tired of manual fault simulation—docs are clear and usage is intuitive—but with 19 stars and 1.0% credibility score, it's early alpha; stick to non-prod and watch for stability updates.

(178 words)