Helidon 27 tracks JDK 27 while 4.5.5 remains the JDK 21 line
Helidon 27 is the first release under Oracle's Tip & Tail model, aligned with JDK 27 while Helidon 4.5.5 stays on a JDK 21 baseline. New Messaging and Data JDBC modules and restructured programming models sit on the Tip side.
The Engineer · Build desk
Teams on JDK 21: Helidon 4.5.5 keeps 4.5 LTS, with JDK 25 support. Tip: Helidon 27 aligns with JDK 27 and the OpenJDK cadence. Tail: critical bugs, security fixes, selected backports. SE users: Helidon Core replaces SE. SE Integrations: now Helidon Extensions, each on its own lifecycle.
- What's now possible capability Teams on JDK 21 Helidon 4.5.5 maintains Helidon 4.5 LTS on its JDK 21 baseline, with support for JDK 25, claim 3
- What it limits constraint Teams tracking the Tip Helidon 27 aligns with JDK 27 and will be updated under the current OpenJDK release cadence, claim 2
- What it limits constraint Teams staying on the Tail The Tail prioritizes critical bugs, security fixes and carefully selected backports, claim 4
- Who has to decide decision Helidon SE users Helidon Core replaces Helidon SE, with two programming models: Imperative and Declarative, claim 7
- What it limits constraint Projects on SE Integrations Moved to its own project as Helidon Extensions; each extension has its own release lifecycle, claim 10
| Who | How | Kind | Claim |
|---|---|---|---|
| Teams on JDK 21 | Helidon 4.5.5 maintains Helidon 4.5 LTS on its JDK 21 baseline, with support for JDK 25 | capability | 3 |
| Teams tracking the Tip | Helidon 27 aligns with JDK 27 and will be updated under the current OpenJDK release cadence | constraint | 2 |
| Teams staying on the Tail | The Tail prioritizes critical bugs, security fixes and carefully selected backports | constraint | 4 |
| Helidon SE users | Helidon Core replaces Helidon SE, with two programming models: Imperative and Declarative | decision | 7 |
| Projects on SE Integrations | Moved to its own project as Helidon Extensions; each extension has its own release lifecycle | constraint | 10 |
What happened
- Helidon 28 will ship with JDK 28 in March 2027, because the Tip follows the OpenJDK release cadence.
- Helidon Core replaces Helidon SE and offers two programming models, Imperative and Declarative.
- Helidon Messaging avoids reactive APIs such as MicroProfile Reactive Messaging and binds Kafka, JMS or Apache Pulsar channels through configuration and pluggable connectors.
- Helidon Data JDBC gives repository queries a unified API over ORM and supports Jakarta Persistence with EclipseLink and Hibernate ORM.
- Helidon SE Integrations moved to its own project as Helidon Extensions, and each extension is maintained under its own release lifecycle.
Why it matters
- Who has to decide decision A team on JDK 21 can move its runtime to JDK 25 and stay on the 4.5 line, so the JDK upgrade and the Helidon upgrade can be scheduled separately.
- What it costs cost Tracking the Tip means a new Helidon version with each OpenJDK release, and someone has to test and schedule every one of them.
- What it limits constraint A team that wants Messaging or Data JDBC should plan on the Tip, since the Tail's stated priorities are critical bugs, security fixes and selected backports.
- Who's exposed exposure Projects built on SE Integrations can no longer assume their extensions share one version, because each now has its own release lifecycle.
The two lines are anchored six JDK releases apart, 27 minus 21 [18]. The version numbers show which side a project is on. Helidon 27 takes its number from JDK 27 [2]. Helidon 4.5.5 stays under the familiar Helidon semantic versioning [6], and the separate Helidon MicroProfile project, which keeps the MicroProfile and Jakarta EE specifications, will follow the same scheme [9].
Declarative is the model to read closely. It uses dependency injection and annotations, and the annotations generate imperative code and wiring at build time [8]. Imperative skips both and uses plain Java [8]. Data JDBC also translates at compile time: interfaces that carry query definitions become implementation classes [14]. We'd expect mistakes in either to fail the build.
Helidon Messaging asks developers for ordinary, blocking Java [12]. The project has a basis for that. Its web server, codenamed Nima and introduced with Helidon 4.0 in October 2023, is based on JEP 444 virtual threads, and it followed the Netty-based server used in the 1.0 to 3.0 release trains [15]. We think the Messaging design follows from that choice.
Helidon 27 is maintained under the Java Verified Portfolio, which InfoQ describes as an ecosystem of Oracle-supported technologies first introduced at JavaOne 2026 [16]. InfoQ's report does not give an end date for 4.5 support. The release notes for 27.0.0 and 4.5.5 carry more detail [17].
In our view, a production service on JDK 21 with no use for the new modules should stay on 4.5.5. The Tail is meant as a more stable and secure baseline [1] and a longer-lived production one [5]. A team already on a current JDK that wants Messaging or Data JDBC should take the Tip and plan an upgrade with each JDK release. That is the right tradeoff for teams that upgrade slowly. Teams that already move JDKs every release give up little by tracking the Tip.
What to watch
- Helidon 28 alongside JDK 28 in March 2027, which will show what a Tip-to-Tip upgrade costs.
- Whether Messaging or Data JDBC are backported to the 4.5 line, which would shrink the reason to leave the Tail.
- An end date for 4.5 support in the 27.0.0 and 4.5.5 release notes.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence55
- Adoption
- Not scored
- Hype gap
- Not scored
- Incentives
- Not scored
- Confidence55
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
Helidon 27 is the first release that follows the Oracle Tip & Tail Model of Library Development, where the Tip adopts the latest Java technology and the Tail provides a more stable and secure baseline.
- [2]
Helidon 27 was released concurrent with JDK 27 and serves as the Tip: it aligns with JDK 27, adopts the latest Java features, and will be updated under the current OpenJDK release cadence.
- [3]
Helidon 4.5.5 serves as the Tail: it maintains Helidon 4.5 LTS on its JDK 21 baseline with support for JDK 25.
- [4]
The Tail prioritizes critical bugs, security fixes and carefully selected backports.
- [5]
The Tail allows for a longer-lived production baseline for development teams.
- [6]
Helidon 4.5.5 is still managed under the familiar Helidon semantic versioning.
- [7]
The release introduces Helidon Core, replacing Helidon SE, with two new programming models: Imperative and Declarative.
- [8]
Imperative allows developers to build applications in plain Java without dependency injection or annotations. Declarative provides dependency injection and annotations that generate imperative code and wiring at build time.
- [9]
Helidon MicroProfile replaces the heritage Helidon MP, has been moved into its own project, and will continue to support the MicroProfile and Jakarta EE specifications and follow the Helidon semantic versioning.
- [10]
Helidon SE Integrations has been moved to its own project and renamed Helidon Extensions; each extension will be independently maintained under its own release lifecycle.
- [11]
Helidon Messaging avoids reactive APIs such as the MicroProfile Reactive Messaging specification, and uses connector-neutral channels such as Kafka, JMS or Apache Pulsar that are bound through configuration and pluggable connectors.
- [12]
With Helidon Messaging, developers can use ordinary, blocking Java.
- [13]
Helidon Data JDBC provides a unified API for data repository queries as an abstraction over traditional ORM, and supports the Jakarta Persistence specification and its implementations EclipseLink and Hibernate ORM.
- [14]
Helidon Data JDBC lets interfaces with query definitions be translated into implementation classes at compile time.
- [15]
The original Netty-based Helidon web server was available in the 1.0 to 3.0 release trains; a new web server, codenamed Helidon Nima and based on JEP 444 Virtual Threads, was introduced with Helidon 4.0 in October 2023.
- [16]
Helidon 27 is maintained under the Java Verified Portfolio, an ecosystem of Oracle-supported technologies first introduced at JavaOne 2026.
- [17]
More details on these releases may be found in the release notes for version 27.0.0 and version 4.5.5.
- [18]
The Tip (aligned with JDK 27) and the Tail baseline (JDK 21) are six JDK releases apart.
- [19]
Helidon 28 will be available with the upcoming release of JDK 28 in March 2027.
Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.
Sources
1 independent publisher whose own reporting we read for this story.
- infoq.comHelidon 27 Introduces Restructured Programming Models and New Messaging and Data Modules
1 article · October 16, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.