21–30 of 31 posts
You get the real deal when you pair it with other tools to analyze and monitor traffic.
Worth the note, I sometimes use this front end in case I want to quickly adjust stuff https://github.com/buckle/toxiproxy-frontend
I wrote the initial version of Toxiproxy back in 2014, but Jacob Wirth took it way beyond during his internship at Shopify. It came out of a need for writing integration tests for resiliency work we did at Shopify back then. [1] We didn't want someone to suddenly re-introduce a hard dependency on e.g. Redis on Shopify's storefronts. The initial prototype was a shell script that used lsof(1) and gdb(1) to close the fi…
https://github.com/dastergon/awesome-chaos-engineering#notab... does list toxiproxy.
Any general pointers for handling network connectivity issues (from any OSI layer) in client and server apps?
Many apps lack 'pending in outbox' functionality that we expect from e.g. email clients.
- [ ] Who could develop a set of reference toxiproxy 'test case mutators' (?) for simulating typical #DisasterRelief connectivity issues?
(In Python, Pytest + Hypothesis + Toxiproxy-python would be useful.)
Anyone know of anything like this but at the TCP level? I would love to have a way of simulating network partitions and different message delays for distributed algorithms implemented in Elixir. In an ideal world I'd be able to hook the elixir send/receive primitives to intercept messages between processes even in a single node.
May or may not be what you're looking for, but you can do lots of this in linux by using tc. https://man7.org/linux/man-pages/man8/tc.8.html Requires care to use and understand, so may not be applicable, but allows introducing latency, jitter, packet loss, etc.
The other fact that caught my interest was the concept of "gamedays". It really about introducing "problems" in the production system randomly and keeping the support staff that manage application incidents on it toes. (More about in this talk: https://www.youtube.com/watch?v=TTfWpHuCJXk)
Anyone know of anything like this but at the TCP level? I would love to have a way of simulating network partitions and different message delays for distributed algorithms implemented in Elixir. In an ideal world I'd be able to hook the elixir send/receive primitives to intercept messages between processes even in a single node.
Isn't this already at a TCP level? HTTP is only used for management of the proxy?
Anyone know of anything like this but at the TCP level? I would love to have a way of simulating network partitions and different message delays for distributed algorithms implemented in Elixir. In an ideal world I'd be able to hook the elixir send/receive primitives to intercept messages between processes even in a single node.
Anyone know of anything like this but at the TCP level? I would love to have a way of simulating network partitions and different message delays for distributed algorithms implemented in Elixir. In an ideal world I'd be able to hook the elixir send/receive primitives to intercept messages between processes even in a single node.
Isn't this already at a TCP level? HTTP is only used for management of the proxy?
Anyone know of anything like this but at the TCP level? I would love to have a way of simulating network partitions and different message delays for distributed algorithms implemented in Elixir. In an ideal world I'd be able to hook the elixir send/receive primitives to intercept messages between processes even in a single node.