The Road to Quarkus 4: Vision, Roadmap, and Timeline #52020
Replies: 12 comments 43 replies
-
|
Is jackson 3 part of this? |
Beta Was this translation helpful? Give feedback.
-
|
Does the "Full alignment with Jakarta 11" include passing a TCK, perhaps the Core Profile? |
Beta Was this translation helpful? Give feedback.
-
|
What do you envision for 3.x once we start release the 4.x CRs? BTW, I think they should be Betas, not CRs. CRs are release candidates, two months before the GA, it will definitely not be a candidate for release :) |
Beta Was this translation helpful? Give feedback.
-
|
"Java Version Baseline: We are targeting Java 25 & 21." - what does having both Java 25 and 21 as baseline mean? some packages will be 25+ and some 21+? |
Beta Was this translation helpful? Give feedback.
-
|
Is "Maven 4 support" a relevant topic? |
Beta Was this translation helpful? Give feedback.
-
|
Maybe Kotlin First-class support (mostly referring to 100% coroutines support) is planned? |
Beta Was this translation helpful? Give feedback.
-
|
Please kill JDK17. Tear off the band aid, people will be forever keeping it if you don't. I'd also love it if you double down on the service discovery but allow for dynamic discovery of services in quarkus. Right now you force all services to be an annotation when having that dynamic will allow me to get rid of the dynamic ones I had to make. Specifically with grpc - a factory that would create client stubs through service discovery... SomeGrpcStub stub = CoolNewFactory.get("stub-instance-a"); |
Beta Was this translation helpful? Give feedback.
-
|
Sth we felt is missing, dynamically (I mean without redeploying) disabling reactive messaging reading from queues. |
Beta Was this translation helpful? Give feedback.
-
|
From our open source java library (Timefold Solver) point of view:
No problem. We intend to release Timefold Solver 2.0 in March 2026 with a minimum of java 21 already and not support Quarkus 4 in Timefold Solver 1.x. I think the ecosystem moves a lot faster these days than 10+ years ago, thanks to Dependabot, more streamlined deployments, CI/develops and less Backwards Compatibility breakage.
Not anything missing, but some timing concerns: We have Jackson integration ( This creates some concerns for us: Hope that helps :) |
Beta Was this translation helpful? Give feedback.
-
|
Nothing on Hibernate / Panache ? |
Beta Was this translation helpful? Give feedback.
-
Is this meant only for the quarkus framework itself? or for applications as well? |
Beta Was this translation helpful? Give feedback.
-
|
How about the old challenge of the core being quite tied to Maven / Gradle in lots of its assumptions of build system and file structure? i.e. at the moment jbang support is more hacked in than nicely fitting. I'm not here suggesting this for jbang only, but also for possibly handling multiple versions of maven/gradle over time, or enable mill, bazel, etc. integration via explicit apis over one off workarounds? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
As we continue to evolve the Quarkus ecosystem, it is time to look ahead to our next major milestone. We are officially kicking off the planning and development phase for Quarkus 4.
Our goal for Quarkus 4 is to leverage the latest innovations in the Java ecosystem (including Project Leyden and JPMS), double down on AI integration, and streamline the architecture to be even more modular and lightweight.
Below is the proposed schedule and the "Big Ticket" items we are targeting.
The Schedule (Tentative)
Please note: This is a no-commitment schedule. These dates represent our current targets and are subject to change based on development progress and upstream dependencies.
Key Themes and Features
We are tracking the detailed work in this GitHub Project. Here are the headlines:
Core Architecture & Standards
We are making significant changes to how Quarkus is built and packaged to ensure long-term maintainability and performance.
Reactive Core & I/O
Building on our reactive roots with the next generation of Vert.x.
AI & LangChain4J.NEXT
Quarkus has become a go-to framework for Java AI development; Quarkus 4 will push this further.
4. Native & AOT
Developer Experience & Compatibility
⠀
This roadmap is a statement of intent. As always, Quarkus is community-driven.
Let's discuss below!
Beta Was this translation helpful? Give feedback.
All reactions