avaje-inject VS Java Faker

Avaje Inject has quickly become one of my favorite libraries. Inject is basically like Dagger if Dagger was focused on server side instead of Android. It's a tiny lib (~76kb) that uses the power of annotation processing to generate DI classes. Recently I've been using it for AWS lambdas and it works pretty great.

https://avaje.io/inject/ - Implements JSR-330 and JSR-250

Have you tried out Avaje inject? It's currently my favorite DI lib.

Been building a web service with avaje inject and avaje http lately. It has a very spring-like feel for a DI lib, (Lifecycles, Test annotations) but the libs are tiny and totally reflection free through codegen.

Avaje is pretty cool, it's a compact DI library based on APT. https://github.com/avaje/avaje-inject

Like avaje inject ? DI as source code generation done at build time?

Just to say, I also created a DI library called avaje-inject - https://avaje.io/inject/ ... which uses Java annotation processing to do DI as mostly source code generation. So the runtime dependency is ~ 67Kb. It also supports AOP aspects via source code gen which I think is kind of cool - you can have your own aspects like `@Retry` etc and it's actually done using source code generation.

I am a bit fan of using annotation processing (source code generation) to simplify things - DI https://avaje.io/inject/ , JSON binding (https://github.com/avaje/avaje-jsonb) and rest servers and clients (https://avaje.io/http).

Dagger2 and avaje-inject are other options (DI as source code generation via annotation processing). https://avaje.io/inject/

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.