The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →In 2023, Java was changing quickly around a stable, predictable release cadence. Java 21 arrived on September 19 as the year’s major platform milestone, while Eclipse Foundation survey respondents showed rising Java 17 use alongside a still-large Java 11 base. For enterprise teams, the practical question was how quickly to modernize without letting compatibility needs and migration costs disrupt production.
What changed in Java in 2023?
Java 21 set the platform’s next long-term baseline
Oracle released Java 21 on September 19, 2023. Oracle described it as the 12th feature release delivered on the six-month release cadence and said it offered at least eight years of support. That cadence made a new feature release a predictable event, while the longer support horizon made Java 21 a significant option for teams choosing a durable upgrade baseline.
Adoption moved forward, but the production base remained mixed
The Eclipse Foundation’s 2023 survey put Java 17 usage among respondents at 36%, up from 26% in its 2022 survey. Java 11 remained more widely used: 50% in 2023, down from 57% in 2022. These figures describe survey respondents, not every Java developer or application, but they show both momentum toward newer Java and the persistence of older production environments.
Should a team upgrade to Java 17 or Java 21?
There was no single best choice for every organization in 2023. Java 21 was the newest long-term-support baseline; Java 17 was a prominent upgrade target in the Eclipse Foundation survey; and Java 11 remained common enough that compatibility could constrain change. The appropriate target depended on the application’s dependencies, deployment environment, support requirements, and the effort needed to test and migrate it.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches| Choice | What it meant in 2023 | Practical consideration |
|---|---|---|
| Java 21 | Released by Oracle on September 19, 2023; Oracle said it offered at least eight years of support. | A new long-term baseline for teams ready to validate their applications and dependencies against it. |
| Java 17 | Used by 36% of Eclipse Foundation 2023 survey respondents, up from 26% in 2022. | A visible modernization target for teams moving off older Java versions. |
| Java 11 | Used by 50% of Eclipse Foundation 2023 survey respondents, down from 57% in 2022. | A large installed base meant migration could require compatibility checks and coordinated application work. |
A sensible upgrade decision starts with the system rather than the version number. Teams should inventory runtimes and frameworks, verify that critical dependencies support the intended Java version, and test the application and deployment process before scheduling production rollout. If existing compatibility requirements make an immediate move impractical, the survey’s Java 11 figure is a reminder that remaining on an older baseline was still common in 2023—not evidence that every application could safely defer modernization.
Is Jakarta EE still relevant?
Yes. The Eclipse Foundation’s 2023 survey showed Jakarta EE remained a major part of enterprise Java, even as adoption of Jakarta EE 10 was still developing. Seventeen percent of respondents reported using Jakarta EE 10, while over 60% said they had already migrated or planned to migrate to Jakarta EE within six to 24 months. Those figures point to active migration, not a completed ecosystem-wide transition.
Rank #2
That incomplete transition matters for organizations operating existing applications. Different Jakarta EE generations could coexist in production, so migration planning needed to account for the application’s current generation, its dependencies, and the work required to move it—not just the availability of a newer specification. Jakarta EE and Spring should also be understood as overlapping but distinct choices, rather than mutually exclusive products.
Which Java framework was best for cloud-native applications?
The 2023 evidence shows that Spring/Spring Boot led reported cloud-native Java framework use, with Jakarta EE also broadly used and MicroProfile present in the mix. The survey figures are not a verdict that one framework suits every application: a team’s existing architecture, skills, dependencies, and migration requirements remain central to the choice.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Framework or platform | Reported use for cloud-native applications | What the figure indicates |
|---|---|---|
| Spring/Spring Boot | 66% of Eclipse Foundation 2023 survey respondents | The most widely reported option in these survey figures. |
| Jakarta EE | 53% of Eclipse Foundation 2023 survey respondents | A major enterprise choice alongside Spring/Spring Boot. |
| MicroProfile | 26% of Eclipse Foundation 2023 survey respondents | A further established option in the cloud-native Java landscape. |
The reported percentages should not be read as exclusive market shares: Spring/Spring Boot and Jakarta EE can appear in the same organization’s wider application landscape, and the figures describe survey respondents rather than all Java users.
How was cloud-native Java adoption changing?
The Eclipse Foundation’s 2023 survey described several routes toward cloud-native deployment, from new or replacement systems to changing existing applications. Respondents reported hybrid architectures at 41%; 28% planned cloud-native replacements; 24% were modifying existing Java applications for cloud migration; and 22% reported Java applications already running in the cloud.
Rank #4
These figures describe different reported situations, not necessarily stages that every organization follows or mutually exclusive groups. Taken together, they show why “moving Java to the cloud” could mean different levels of change: operating across hybrid environments, replacing an application, adapting an existing one, or running Java applications in the cloud already. Eclipse Foundation Executive Director Mike Milinkovich characterized the broader direction in 2023 as continued growth of cloud-native Java, with open source leading the way.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What should Java teams take from the 2023 picture?
- Choose a target based on support and compatibility. Java 21 offered the newest long-term-support baseline in 2023, while Java 17 was a prominent upgrade target and Java 11 remained widely used.
- Plan framework and platform work alongside the runtime upgrade. Spring/Spring Boot, Jakarta EE, and MicroProfile all appeared in the cloud-native landscape, while Jakarta EE 10 adoption remained incomplete.
- Define the migration scope. A cloud initiative might involve hybrid operations, replacing a system, modifying an existing Java application, or deploying applications already prepared for the cloud.
- Budget for production maturity and migration effort. Survey momentum toward newer Java and cloud-native deployment did not remove the compatibility and coordination work associated with established systems.
This article describes the ecosystem as reported in 2023. Adoption and support conditions can change after that year, so these figures should not be treated as a current snapshot.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
