Flashcards

Flashcard Study

Java: WebFlux vs Virtual Threads

Front

How would you explain the Reactive Streams Specification in an interview?

Defines interfaces like Publisher and Subscriber for handling data streams. The Reactive Streams Specification standardizes asynchronous stream processing…

View Card →

Flashcard Study

Java: WebFlux vs Virtual Threads

Front

How do Non-Blocking Event Loops work in WebFlux?

Requests are processed without waiting for blocking operations. Non-Blocking Event Loops allow WebFlux to handle many requests on…

View Card →

Flashcard Study

Java: WebFlux vs Virtual Threads

Front

How would you explain the Thread-Per-Request model in an interview?

A separate thread is created for each request. In the Thread-Per-Request model, each incoming client request is handled…

View Card →

Flashcard Study

Java: WebFlux vs Virtual Threads

Front

Why do virtual threads often win for ordinary CRUD services?

They keep imperative code readable while reducing the cost of many blocked waits. Virtual threads do not replace…

View Card →

Flashcard Study

Java: WebFlux vs Virtual Threads

Front

When is WebFlux usually worth its complexity?

When the workload is stream-heavy or holds many slow connections open concurrently. WebFlux shines when the system is…

View Card →

Flashcard Study

Java: Thread-Per-Request Bottleneck

Front

WebFlux vs Virtual Threads?

WebFlux uses non-blocking I/O, Virtual Threads use lightweight threads. WebFlux leverages non-blocking I/O to handle many connections with…

View Card →

Flashcard Study

Java: Thread-Per-Request Bottleneck

Front

The Danger of Blocking the Event Loop?

Blocking the event loop can lead to performance issues. Blocking the event loop prevents it from handling other…

View Card →

Flashcard Study

Java: Thread-Per-Request Bottleneck

Front

Mono vs Flux in Project Reactor?

Mono for single values, Flux for multiple values. In Project Reactor, Mono represents a single value or an…

View Card →

Flashcard Study

Java: Thread-Per-Request Bottleneck

Front

Reactive Streams Specification: Publisher and Subscriber?

Publisher emits data, Subscriber processes it. In the Reactive Streams specification, a Publisher generates data and sends it…

View Card →

Flashcard Study

Java: Thread-Per-Request Bottleneck

Front

Non-Blocking Event Loops vs Thread-Per-Request?

Non-blocking event loops can handle more concurrent connections efficiently. Non-blocking event loops use a small number of threads…

View Card →