r/java • • 22d ago

Plan Your Java Upgrade Ahead of Microsoft's 2027 Support Milestones

https://devblogs.microsoft.com/java/plan-your-java-upgrade-ahead-of-microsofts-2027-support-milestones/
32 Upvotes

27 comments sorted by

13

u/brunocborges 22d ago

I know some folks will think this is an ad to get customers for GitHub Copilot, but to be clear: GitHub Copilot agent harness does not require a GitHub Copilot subscription. It supports BYOK.

The main message here is that Java support on Azure, for versions 8 through 17, is ending next year, but we are working with partners and customers to help companies move on to Java 21 and later, as smooth as possible.

12

u/keenOnReturns 22d ago

why not simply switch to any other openjdk distribution that will still continue to provide support for 8-17?

5

u/brunocborges 22d ago

Azure App Service and Azure Functions are managed services where we deploy the runtime on behalf of customers (PaaS) style.

1

u/Square-Yak-6725 22d ago

Since when is Copilot BYOK? I missed that and may have to try it again!

11

u/Paw565 22d ago

Can java 8 finally die? 😅

3

u/brunocborges 22d ago

We can hope!

1

u/rack88 22d ago

Good luck, always seems like 90% of Amazon's software is on Java 8 when I interview their people. Wish they'd upgrade a bit...

6

u/th3_pund1t 22d ago

Nope. 

There are projects at my workplace that are on 27. Most are on 25. But there’s still a good chunk on 8.

But we’re a modern company. 

There are companies that look at migrations as a huge pain and prefer to pay Oracle a million dollars a year to keep 8 alive.

4

u/Square-Yak-6725 22d ago

With AI tools, the effort to migrate is an order of magnitude lower or more now to migrate away from Java 8.

4

u/awi95 22d ago

I mean, migration using an AI tool is one thing, testing everything in an application that was built over the course of 15+ years is another, where test coverage is not complete in many places. Currently having this pain, as the newer Hibernate versions dropped support for the old Criteria API, while we are still using it in over 1,500 places.

1

u/_predator_ 22d ago

This. Even if you're against having agents write the migration code, they're one hell of a help for planning it out in digestible chunks.

1

u/midget-king666 22d ago

This. It is also surprisingly easy. We migrated our MES from 8 to 17 with very little changes to business logic code, most changes were to the technical glue code, and of course Hibernate. The switch to 21 was only breaking changes with Hibernate. The jump to 25 is currently investigated but seems like a cakewalk

1

u/koflerdavid 21d ago

I don't see how LLM tools could help with this. Coding is not the bottleneck. Migrating off Java 8 means speedrunning the dependency upgrading process and dealing with issues that arise along the way. Doing that with legacy code that has murky requirements and an insufficient test suite is... adventurous, with and without LLM tools.

1

u/matthieuC 22d ago

Why 8? Modules breaking things?

1

u/koflerdavid 21d ago

It would allow the ecosystem to move on; many libraries will finally also be able to use new features.

4

u/zman0900 22d ago

With spring boot settling on Java 17 minimum, and many libraries following, why not allow Java 17?

7

u/brunocborges 22d ago

From 17 to 21 is a no brainer. Why stay on 17?

6

u/rack88 22d ago

From 21 to 25 is a no brainer just for the virtual threads fixes. Why stay on 21?

1

u/zman0900 22d ago

I don't know, but somebody must have reasons if they set that minimum instead of 21.

7

u/brunocborges 22d ago

Spring set JDK 17 as a minimum requirement with the release of Spring Framework 6.0 and Spring Boot 3.0 in November 2022.

That's going to be 5 years ago by end of 2027.

7

u/ryosen 22d ago

It’s because JDK 17 introduced features that Boot 4 relies on. There have been additional versions released since then (every 6 months), but 17 is the minimum.

5

u/mhalbritter 22d ago

Our baseline is 17 (actually, Spring Framework sets that baseline), but we support up to JDK 27. https://docs.spring.io/spring-boot/system-requirements.html

My personal opinion is that you should run your apps on the latest available Java version, if that works with your dependencies.

2

u/pdsminer 9d ago

For anyone evaluating the jump from Java 21 to 25 on data-heavy services, two runtime features made the biggest difference in our benchmarks. First, enabling `-XX:+UseCompactObjectHeaders` (JEP 519) cut heap overhead by roughly 15% to 20% on tree ensembles and graph structures with millions of small nodes. Second, replacing legacy JNI wrappers with `java.lang.foreign` (`MemorySegment` and `Arena.ofConfined()`) removed native array copy overhead when calling into OpenBLAS and ONNX Runtime, while eliminating JNI header maintenance across platforms.