In this project, we will create six applications using Spring Boot, Quarkus, and Micronaut frameworks.
For each framework, we will implement one app with traditional blocking Web using Apache Tomcat and another app with non-blocking Reactive using Netty. We will also build both JVM and Native Docker images for the applications.
For the Spring Boot apps, we will build additional Docker images with different configurations, including enabling or not some Java optimizations like Virtual Threads (JEP 444), CDS (JEP 310), and AOT (JEP 295).
On ivangfr.github.io, I have compiled my Proof-of-Concepts (PoCs) and articles. You can easily search for the technology you are interested in using the filter. Who knows, perhaps I have already implemented a PoC or written an article about what you are looking for.
- [Medium] Spring Boot Performance Benchmark: Web, Reactive, CDS, AOT, Virtual Threads, JVM, and Native
- [Medium] Spring Boot 3.3.2 Benchmark: Web, Reactive, CDS, AOT, Virtual Threads, JVM, and Native
- [Medium] Spring Boot 3.3.4 Benchmark: Web, Reactive, CDS, AOT, Virtual Threads, JVM, and Native
- [Medium] Spring Boot 3.4.3 Benchmark: Web, Reactive, CDS, AOT, Virtual Threads, JVM, and Native
- [Medium] Spring Boot 3.5.3 Benchmark: Web, Reactive, CDS, AOT, Virtual Threads, JVM, and Native
- [Medium] Spring Boot 4.0.2 Benchmark: Web, Reactive, CDS, AOT, Virtual Threads, JVM, and Native
- [Medium] Spring Boot 4.0.2 Benchmark (Java 21 vs. 25): Web, Reactive, CDS, AOT, Virtual Threads, JVM, and Native
- [Medium] Java Frameworks Performance Benchmark: Spring Boot vs. Quarkus vs. Micronaut
- [Medium] Performance Benchmark: Spring Boot 3.3.2 vs. Quarkus 3.13.2 vs. Micronaut 4.5.1
- [Medium] Performance Benchmark: Spring Boot 3.3.4 vs. Quarkus 3.15.1 vs. Micronaut 4.6.3
- [Medium] Performance Benchmark: Spring Boot 3.4.3 vs. Quarkus 3.19.3 vs. Micronaut 4.7.6
- [Medium] Performance Benchmark: Spring Boot 3.5.3 vs. Quarkus 3.24.3 vs. Micronaut 4.9.1
- [Medium] Performance Benchmark: Spring Boot 4.0.2 vs. Quarkus 3.31.1 vs. Micronaut 4.10.7
| Framework | Version |
|---|---|
| Quarkus | 3.31.1 |
| Micronaut | 4.10.7 |
| Spring Boot | 4.0.2 |
For fair benchmark comparison, the blocking Web MVC applications (spring-boot-greetings-api-web, quarkus-greetings-api-web, and micronaut-greetings-api-web) are configured with 200 threads:
| Framework | Configuration Property | Default (without config) |
|---|---|---|
| Spring Boot | Tomcat default | 200 |
| Quarkus | quarkus.thread-pool.max-threads=200 |
Math.max(8×CPU, 200) |
| Micronaut | Tomcat default | 200 |
This ensures all three frameworks use the same number of worker threads during benchmarks.
Virtual threads are disabled in all blocking applications Web MVC applications (spring-boot-greetings-api-web, quarkus-greetings-api-web, and micronaut-greetings-api-web) to ensure fair benchmark comparison. The table below shows the default virtual threads setting for each framework:
| Framework | Virtual Threads | Configuration |
|---|---|---|
| Spring Boot | Disabled by default | - |
| Quarkus | Disabled by default | - |
| Micronaut | Enabled by default | micronaut.servlet.enable-virtual-threads=false |
This ensures all three Web applications use regular platform threads (200 max by default) during benchmarks.
The application's JVM and native Docker images can be found at this Docker Hub link.
- build-docker-images-spring-boot.sh: script to build Spring Boot Docker images
- build-docker-images-quarkus.sh: script to build Quarkus Docker images
- build-docker-images-micronaut.sh: script to build Micronaut Docker images
- remove-docker-images.sh: script to remove all Docker images
If you find this useful, consider buying me a coffee:
This project is licensed under the MIT License.
