Quarkus Community Call - 2026-03-03

[cescoffier]

Hello,

Yesterday, we had our latest public Quarkus community call.

Here is a short summary. You can find the complete minutes on
https://docs.google.com/document/d/1TgFZsuOQo9qZ4CnQII5LHhQVgMC6YsVMs1UJIAJooyM/edit?usp=sharing.

You can watch the recording here: https://drive.google.com/file/d/1dTafGBEd4fJ7wRwr-rx1kAp_QBHadnIC/view?usp=sharing

The slides presented during the call are available here: https://drive.google.com/file/d/10s3MP8yVCRFJtLji0QugcdR9JJouxRkY/view?usp=sharing

Recap:
Clement opened the call by announcing that the new public benchmark numbers and Holly's accompanying blog post are now live on quarkus.io. He also issued an urgent call for the community to test Quarkus 3.32, which will serve as the foundation for the upcoming 3.33 LTS release, emphasizing that only bug fixes are being accepted right now.

The core of the meeting, led by Ladislav and Julien, focused on the complexities of the Quarkus concurrency model, specifically the intersection of Vert.x event loops and worker threads. Ladislav presented his ongoing PR to officially document this model. The team dug into the ambiguity of the Vert.x "safe" context toggle, noting that it conflates "isolation" with "lack of concurrency" (the latter being strictly required by extensions like Hibernate Reactive). Clement, Stéphane, and Yoann debated the validity of "nested contexts"; while the current implementation is considered a hack for OpenTelemetry, the use case remains valid for features like @transactional scoping.

Julien highlighted that while linear context propagation works well, Quarkus currently lacks the tools for users to safely express fan-in and fan-out concurrency boundaries. Furthermore, Ozan and Bruno discussed context propagation in reactive messaging, agreeing that while tracing links should be maintained across brokers, passing MDC context by default risks PII leaks. There was broad agreement that a robust, newly designed Context Propagation API is a hard requirement for Quarkus 4, and that the core team will begin discussing it at next week's face-to-face meeting.

[hantsy]

It seems Spring used Micrometer Context Propagation https://docs.micrometer.io/context-propagation/reference/usage.html to pass contextual data(security, transaction, etc.) in multiple thread(async), reactive streams background(multiple threads, or event loop, etc.), and Kotlin Coroutines continuation seamlessly. The end developers do not need to call some CP APIs explicitly.

Microprofile CP seems not flexible like Spring env.

[cescoffier]

That's not totally exact. We have the same kind of support, sometimes even better. However, we are also seeing new patterns emerging that are less linear and require more complex context management/API, and that can be ambiguous. I recommend checking the 2 recordings on context propagation, they provide a good overview of the current solutionS, and the new patterns we are seeing.