Additional Notes
Non-Blocking Event Loops vs Thread-Per-Request?
Track: Java
Topic: Reactive Streams
Focus: Thread-Per-Request Bottleneck
Java: Thread-Per-Request Bottleneck
Answer
Non-blocking event loops can handle more concurrent connections efficiently.
Non-blocking event loops use a small number of threads to handle many connections by only working on connections that are ready, freeing up resources for other tasks. For example, in a WebFlux application, a single thread can handle multiple WebSocket connections for live price updates without waiting for each connection to complete, unlike thread-per-request.
Non-blocking event loops use a small number of threads to handle many connections by only working on connections that are ready, freeing up resources for other tasks. For example, in a WebFlux application, a single thread can handle multiple WebSocket connections for live price updates without waiting for each connection to complete, unlike thread-per-request.
Topics: Java Reactive Streams Thread-Per-Request Bottleneck