Well, to tell the truth, both MVC and WebFlux are equally well supported — no bias here.
But the real magic of the reactive stack lies in the fact that it’s fully asynchronous straight out of the box. Every DataFetcher runs asynchronously, and queries (including all those nested subqueries) that are invoked in parallel actually execute in parallel. This help a lot according to my experience :)

That gives you an impactful performance boost, especially when you start playing with GraphQL namespacing techniques — where multiple query segments can resolve simultaneously without blocking the main thread.

Another day, another WebFlux win. GraphQL Java defines subscriptions as reactive-stream Publishers, so Flux/Mono it is — or Observable, if you’re still dabbling in the dark arts of RxJava. 🧙‍♂️

Reactive all the way ;) 🚀