How to add latency to HTTP responses with Muxy?

Use the Delay middleware in your config.yml, setting response_delay in milliseconds. For example, add a 5-second delay by specifying response_delay: 5000 and running Muxy as a proxy for your target service.

Muxy vs Toxiproxy for TCP chaos engineering?

Muxy offers broader layer coverage (L4, L5, L7) with HTTP tampering and extensible plugins, while Toxiproxy is simpler but focused on TCP. Choose Muxy for multi-layer simulations or Toxiproxy for lightweight TCP-only scenarios.

How to integrate Muxy with Docker Compose?

Use the official Docker image, mount your config.yml as a volume, and run it as a privileged container to allow network shaping. The README provides a Docker run example that can be adapted for Compose definitions.

Can Muxy simulate packet loss for mobile app testing?

Yes, use the Network Shaper middleware to set packet_loss as a percentage in the config. This operates at Layer 4, allowing you to target specific IPs and ports to mimic unreliable network conditions.

Does Muxy support SSL/TLS termination for HTTPS proxies?

Yes, the HTTP Proxy configuration allows specifying SSL keys and certificates for both server and client sides, enabling secure proxy setups with optional insecure mode for testing untrusted targets.

How to create custom middleware in Muxy?

Implement the Middleware interface from the codebase, register it via PluginFactories, and add it to your config. The README points to the HTTP Delay symptom as an example for extending functionality.

Open-Awesome

muxy

MITGov0.0.5

A proxy tool for chaos engineering that simulates real-world distributed system failures to test application resilience.

GitHub

828 stars31 forks0 contributors

What is muxy?

Muxy is a chaos engineering proxy tool that simulates real-world distributed system failures to test application resilience. It operates at network layers 4, 5, and 7, allowing developers to inject faults like latency, packet loss, and HTTP errors into their systems. The tool helps identify weaknesses in fault tolerance mechanisms before they cause production outages.

Target Audience

Developers and engineers building distributed systems, microservices, or APIs who need to validate resilience patterns and fault tolerance strategies. It's particularly valuable for teams practicing chaos engineering or implementing circuit breakers like Hystrix.

Value Proposition

Muxy provides a lightweight, extensible, and easy-to-configure solution for chaos testing without complex dependencies. Its modular architecture and Docker support make it adaptable for both local development and automated CI/CD pipelines, offering granular control over failure injection scenarios.

Overview

Chaos engineering tool for simulating real-world distributed system failures

Use Cases

Best For

Testing circuit breaker implementations like Hystrix in microservices
Simulating network partitions in distributed architectures
Validating application behavior under high latency or packet loss conditions
Automating resilience tests in continuous integration workflows
Injecting HTTP errors and tampering with API responses
Shaping network traffic for mobile or IoT device testing

Not Ideal For

Teams requiring parallel chaos testing across multiple test suites
Environments where root access is unavailable or Windows is the primary OS
Projects needing only high-level HTTP mocking without network-layer interference

Pros & Cons

Pros

Multi-Layer Chaos Simulation

Operates at network layers 4, 5, and 7, allowing comprehensive failure injection from TCP sessions to HTTP responses, as shown in the proxy and middleware configurations.

Extensible Plugin Architecture

Modular design with proxies and middleware that can be extended using the Plugo system, enabling custom chaos scenarios beyond built-in features.

CI/CD Integration Ready

Designed for automated resilience testing in continuous integration pipelines, with Docker support and YAML configuration for easy deployment in containerized environments.

Precise Targeting Rules

Advanced regex-based matching allows fine-grained control over which requests receive chaos, such as specifying methods, paths, and hosts for failure injection.

Cons

Stateful and Non-Parallel

Cannot be run in parallel with other tests due to its stateful nature that interferes with low-level networking, limiting scalability in large test suites.

Root Access and OS Limitations

Some middleware like the Network Shaper requires root privileges and only works on specific OSes (MacOSX, FreeBSD, Linux), hindering use in restricted or Windows-heavy environments.

Complex Configuration Overhead

Setting up advanced scenarios with multiple proxies and middleware involves detailed YAML files and regex rules, which can be error-prone and time-consuming for new users.

Frequently Asked Questions

Related Projects

okhttp

A meticulous HTTP client for the JVM, Android, and GraalVM.

Stars47,011

Forks9,283

Last commit22 hours ago

gor

GoReplay is an open-source tool for capturing and replaying live HTTP traffic into a test environment in order to continuously test your system with real data. It can be used to increase confidence in code deployments, configuration changes and infrastructure changes.

Stars19,300

Forks90

Last commit5 months ago

comcast

Simulating shitty network connections so you can build better systems.

Stars10,510

Forks378

Last commit1 year ago

Aeron

Efficient reliable UDP unicast, UDP multicast, and IPC message transport

Stars8,753

Forks1,070

Last commit23 hours ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub