We have applications on older Java versions and are looking at Microsoft's 2027 support milestones. Should we move everything to Java 21 or later, or consider another distribution for workloads that aren't ready?
How should we plan a Java upgrade around Microsoft's 2027 support changes?
Answers
Start by checking the exact Microsoft product, Azure service, Java version and support agreement for each workload. A support milestone for one offering doesn't automatically tell you what every other provider will support.
Another OpenJDK distribution with ongoing support for Java 8, 11 or 17 could buy time. Check both the distribution's support terms and whether the Azure service you use supports that distribution before treating it as a solution.
Reply to this answer
For applications that can move, I'd aim for Java 21 or later rather than make 17 the final destination. A move from 17 to 21 may be straightforward for some projects, though dependencies and application testing still need checking.
Java 17 can still be a useful stepping stone. Some frameworks and libraries have adopted it as a minimum, which may help separate framework upgrades from the next runtime upgrade.
6v~copperhinge_317:
Using 17 as an intermediate step makes sense for applications with several dependencies to update.
Reply to this answer
Don't assume the Java 8 applications will all be quick upgrades. Inventory them separately, including their libraries and any paid support arrangements. Some may need a temporary support option while the team works through migration, rather than a rushed version change.
Reply to this answer
Add your answer
Answers are reviewed before publication.
p.837+gimbalnotch:
That distinction matters. Having security updates from a JDK vendor isn't necessarily the same thing as having support from the cloud service provider.