Oracle and the OpenJDK community shipped JDK 27 on 15 September 2026, right on the six-month schedule. For most Indian Java teams the release is less about rushing to upgrade and more about planning: which LTS to standardise on, and how framework support windows line up with it.

Facts in this article were checked against OpenJDK, Oracle and Spring project sources in October 2026.

What happened

JDK 27 reached general availability on 15 September 2026. Oracle’s announcement describes it as the 18th feature release delivered on time under the six-month cadence. The release contains nine JDK Enhancement Proposals (JEPs), of which four are previews and one is an incubator feature.

The rampdown followed the usual pattern. ADTmag reported that Rampdown Phase One began on 4 June 2026, with release candidates on 6 August and 20 August before the September GA.

JDK 27 is not a long-term support (LTS) release. Oracle says it will provide updates to JDK 27 only until March 2027, when JDK 28 replaces it.

The nine JEPs in JDK 27

JEPFeatureStatus
523Make G1 the default garbage collector in all environmentsFinal
527Post-quantum hybrid key exchange for TLS 1.3Final
534Compact object headers by defaultFinal
536JFR in-process data redactionFinal
531Lazy constantsThird preview
532Primitive types in patterns, instanceof and switchFifth preview
533Structured concurrencySeventh preview
538PEM encodings of cryptographic objectsThird preview
537Vector API12th incubator

The changes most teams will notice

  • G1 everywhere (JEP 523): earlier, the JVM picked G1 only on machines it treated as server-class. Now the HotSpot JVM selects G1 by default in all environments, including small containers. If your containers have relied on the old fallback to Serial GC, check memory and latency after upgrading.
  • Compact object headers by default (JEP 534): object headers shrink from 96 bits to 64 bits on 64-bit platforms. That can reduce heap use for applications that allocate many small objects, which describes a lot of typical Spring and microservice code.
  • Post-quantum TLS (JEP 527): TLS 1.3 gains a hybrid key exchange that combines a classical algorithm with a quantum-resistant one. This matters most for banks, fintechs and government projects that are starting to plan for post-quantum cryptography.
  • JFR data redaction (JEP 536): Java Flight Recorder can redact sensitive data inside the process. That helps teams share profiling data with vendors without leaking secrets, which is relevant under India’s data protection rules.

Why Java 25 is still the version to standardise on

Oracle’s Java SE support roadmap lists Java 25 (September 2025) as the current LTS. Its Premier Support runs to September 2030 and Extended Support to September 2033. Java 21 (September 2023) remains supported too, with Premier Support until September 2028.

Non-LTS releases are short-lived. Java 26 (March 2026) reached the end of Premier Support in September 2026, and Java 27 ends in March 2027. The roadmap names Java 29, due in September 2027, as the next planned LTS. Oracle intends to ship an LTS every two years.

ReleaseGATypeOracle Premier Support until
Java 21Sept 2023LTSSept 2028
Java 25Sept 2025LTSSept 2030
Java 26Mar 2026Feature releaseSept 2026
Java 27Sept 2026Feature releaseMar 2027
Java 29 (planned)Sept 2027LTSSept 2032

For service companies maintaining client systems, and for GCC teams with strict change control, this table is the practical takeaway. Run production on 21 or 25, and use 27 in CI to catch problems early.

How Spring Boot timelines fit in

Many Indian enterprise backends run on Spring Boot, so the framework calendar matters as much as the JDK calendar.

  • Spring Boot 4.1.0 was announced on the Spring blog on 10 June 2026. InfoQ’s coverage lists gRPC auto-configuration, SSRF mitigation for HTTP clients, lazy datasource connections and Kotlin 2.3 support. It keeps the Java 17 baseline and builds on Spring Framework 7.0.
  • According to the endoflife.date tracker, open-source support for Spring Boot 3.5 ended on 30 June 2026, and Spring Boot 4.0 open-source support runs to 31 December 2026. Commercial support runs longer for customers who pay for it.

The practical result: a team still on Spring Boot 3.x without a commercial support contract is no longer getting free open-source fixes. Moving to Spring Boot 4.x on Java 21 or 25 is the safest path for most projects.

What Indian developers should do now

  1. Pin your LTS. If you are on Java 8, 11 or 17, plan a move to Java 21 or 25. Java 25 gives the longest runway.
  2. Add JDK 27 to CI as a non-blocking job. This shows early whether the G1 default or compact headers change behaviour in your containers.
  3. Check memory limits in Kubernetes. A different default collector can change heap sizing. Watch pod restarts and GC pause metrics after any JDK change.
  4. Plan the Spring Boot 4 migration. Spring Boot 4 is built on Spring Framework 7. Budget time for dependency updates and test fixes.
  5. Don’t use preview features in production code. Structured concurrency and lazy constants are still previews in 27. They need the --enable-preview flag and may change.
  6. Update your resume keywords carefully. Recruiters search for “Java 17”, “Java 21” and “Spring Boot 3/4”. Only list versions you have actually shipped with.

Career angle

For job-seekers, JDK 27 itself is unlikely to show up in interviews. Questions about virtual threads (final in Java 21), records, pattern matching and garbage collector choice come up far more often. Knowing why G1 is now the default everywhere, and what compact object headers do to memory, is a good way to show you follow the platform. Interviewers in product companies and GCCs like that kind of answer.

Frequently asked questions

Is Java 27 an LTS release?

No. Java 27 is a feature release. Oracle will provide updates until March 2027, when Java 28 replaces it. Java 25 is the current LTS, and Java 29 (September 2027) is the next planned LTS.

Should I upgrade production from Java 21 to Java 27?

For most teams, no. Moving to Java 25 makes more sense, since it has Oracle Premier Support until September 2030. Use Java 27 in test pipelines to prepare for future changes.

Does Spring Boot 4.1 need Java 21?

No. According to InfoQ, Spring Boot 4.1 keeps a Java 17 minimum baseline. A few optional integrations need newer Java versions, so check the release notes for the libraries you use.

Official sources

Leave a Reply

Trending