Awaitility VS Java Faker

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.

Faker was originally written in Perl and is also available as a library for Ruby, Java, and Python.

you can use faker java

JavaFaker for generating random data https://github.com/DiUS/java-faker

I've been using https://github.com/DiUS/java-faker which seems to be much more popular. How is this one different?

I'm using 1.0.2 from this repository: https://github.com/DiUS/java-faker

I'm Java developer. While we have had our fair share of shenanigans, if the people behind the Java equivalent of faker (https://github.com/DiUS/java-faker) went off the rails it wouldn't be anywhere near as much of an issue.

This has another bottleneck, each time you request something, it ends up with a IO call to open a file, as all fake data is stored in a file: https://github.com/datafaker-net/datafaker/blob/master/src/main/resources/en/dragon_ball.yml I recently filed a bug to javafaker that in some cases file descriptor was never closed, resulting in even worse performance and memory leaks, killing our service after millions of method calls.