Quarkus vs. Wildfly - The RAM Perspective

quarkus.io (hotspot and native) vs. wildfly.org - memory consumption of the same application (MicroProfile Config, JSON-B, JAX-RS, CDI) deployed on both runtimes.
See you at: workshops.adam-...

[@TheArtiston]

Is it possible to build a large app in quarkus (Like we usually do with Spring, Wildfly, RoR...) without microservices and kubernetes?

[@kevinfleischer2049]

you mean with large a monolyth?
I guess nothing stops you from doing it. The biggest advantage of Quarkus is its low footprint and quick startup, which makes it ideal for container use cases. The monolyths I know of, are "start once, run forever" types. There the only advantage that quarkus brings is the "developer joy" part. But thats not to be ignored.

[@bauer8888]

Hi Adam, nice video!
I created a similar automatic performance test project, comparing Quarkus with Payara Micro and visualizing the results (memory, CPU and time to first request) in diagrams.
github.com/rmh78/quarkus-performance
Your approach using Apache benchmarking tool looks interesting to me.

[@bienadam]

Looks good! Thanks for the link