Awaitility VS toxiproxy

I’ve coded in Java since the first beta, even back then threads were at the top of my list of favorite features. Java was the first language to introduce thread support in the language itself, it was a controversial decision back then. In the past decade, every language raced to include async/await and even Java had some third-party support for that… But Java zigged instead of zagging and introduced the far superior virtual threads (project Loom). This post isn’t about that.

I hope everybody knows https://github.com/awaitility/awaitility by now.

And finally the tests, using Awaitility as we are testing asynchronous stuff:

awaitability: A tool to express expectations for asynchronous system in an easy and concise manner.

Awaitility with version 4.1.0 comes with fail fast feature (2m read) 🎉 https://github.com/awaitility/awaitility/wiki/Usage#fail-fast-conditions

Given our new functionality to update the membership list, we can create a new test case where two nodes join the cluster and expect that to be reflected in the local state of each node eventually. Thanks to the Awaitility DSL we can conveniently wait for the eventual update to happen.

Nota: para los que no la conozcáis, await es un operador de awaitility, muy útil para validación de resultados en procesos asíncronos.

Checkout also shopify's awesome tool called toxiproxy: https://github.com/Shopify/toxiproxy

It turns out to be also a very good way to test a networking library by implementing it. Since your stack needs to be able to basically handle most adverse events properly.

The idea behind 'chaos engineering' is cool.

I use this to simulate delays between various local services:

https://github.com/Shopify/toxiproxy

If you have Docker all you need is a few terminal commands

Idk about firewall level, but application level I’d recommend https://github.com/Shopify/toxiproxy

That's why I usually recommend anybody that develops network critical apps to test their app with something like toxiproxy and purposfully mess with their connections and simulate network issues.

We use this thing. https://github.com/Shopify/toxiproxy I am not sure that it supports windows, but you can install it to the Linux machine and route your application under the test to that proxy.

On the same vibes as https://github.com/Shopify/toxiproxy

https://github.com/Shopify/toxiproxy is a perfect solution for that. I used it quite successfully years ago and it looks like it's still pretty active.

Looking at the toxiproxy you mentioned, it seems like it should do what you want though? TLS is generally over TCP anyway, so it should still be able to throttle those connections - it just wont understand the encryption. I also saw a pull request for having it act as a TLS man-in-the-middle proxy: https://github.com/Shopify/toxiproxy/pull/270