# Spring WebFlux

> Very high concurrency on one loop per process, and 20% slower to build and debug. A blocking call stalls the loop, and the JVM still warms up. 400 MB.

## Trade-offs

| Axis | Score |
| --- | --- |
| Throughput | |
| Tail latency | |
| Memory | |
| Velocity | |
| Resilience | |
| Operability | |

## Frameworks

- [Spring Boot](https://wiki.playquorum.dev/frameworks/spring-boot.md)
- [Quarkus](https://wiki.playquorum.dev/frameworks/quarkus.md)

## Engineering terms

- [Event loop](https://wiki.playquorum.dev/glossary/event-loop.md)
- [JIT warmup](https://wiki.playquorum.dev/glossary/jit-warmup.md)
- [GC pause](https://wiki.playquorum.dev/glossary/gc-pause.md)

## Facts

Spring WebFlux
- **Language:** Java
- **Concurrency:** One event loop
- **Speed:** ×1.1
- **Memory:** 100 MB
- **Startup:** 20 s
- **Warm-up:** 30 s
- **GC pause:** 30 ms
- **Unlocked by:** [Spring WebFlux](https://wiki.playquorum.dev/research/webflux.md)
- **Velocity:** ×0.9
- **Salary:** ×1.05
- **Build:** 6 min

## See also

- [Runtimes and frameworks](https://wiki.playquorum.dev/runtimes.md)
- [Spring Boot](https://wiki.playquorum.dev/frameworks/spring-boot.md)
- [Quarkus](https://wiki.playquorum.dev/frameworks/quarkus.md)

Source: https://wiki.playquorum.dev/runtimes/webflux