Question 1

How do I test Redis failover with Toxiproxy?

Accepted Answer

Configure a proxy for Redis, then use the 'down' toxic or client library to simulate downtime in a test block. The README example shows taking down all Redis instances to verify error handling in a Rails app.

Question 2

Toxiproxy vs iptables for network simulation: which is better?

Accepted Answer

Toxiproxy is cross-platform and doesn't require root access, making it ideal for testing and CI. iptables is Linux-only and lower-level, better for system-wide network control but harder to automate in tests.

Question 3

Can Toxiproxy simulate packet loss?

Accepted Answer

Not directly, but you can use the 'slicer' toxic to break data into pieces or 'timeout' to drop connections, mimicking packet loss effects. For precise packet-level control, tools like 'tc' are more suitable.

Question 4

How to run Toxiproxy in a Docker Compose setup?

Accepted Answer

Use the official Docker image and expose port 8474 for the HTTP API. Configure proxies to intercept service traffic, often using host networking or custom bridge networks to connect containers.

Question 5

Why does Toxiproxy not work with MySQL on localhost?

Accepted Answer

MySQL may prefer Unix domain sockets over TCP when set to 'localhost'. Use '127.0.0.1' as the host and disable sockets in MySQL config, as mentioned in the README's FAQ section.

Question 6

How to add latency to an HTTP service with Toxiproxy?

Accepted Answer

Create a proxy for the HTTP service's TCP port, then apply the 'latency' toxic via the HTTP API or client. Ensure your app routes requests through the proxy's listen address to inject delays.

toxiproxy

What is toxiproxy?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions