Java Support: What's changing

© Copyright Azul Systems 2018
@speakjava
Java Support: What's
Changing and How This
Will Impact Your Business
Simon Ritter
Deputy CTO, Azul Systems
1

Quick Poll
 How quickly do you move to a new release of Java?
1. We deploy it in production before it's released
2. As soon as the release is Generally Available (GA)
3. We wait for a few updates to ensure stability
4. When public updates for the previous release end
5. There are new versions of Java?
2

Java Until Now

Java Platform Development
 Development of releases takes time
– JDK 6: 2 years and 2 months after JDK 5
4

Migrating To A New Version
 Plenty of time to continue with previous release
– JDK 6: 2 years and 11 months of public JDK 5 updates
– JDK 7: 1 year and 9 months of public JDK 6 updates
– JDK 8: 1 year and 1 month of public JDK 7 updates
 Also allows for stabilisation of new platform before
migrating applications in production
5

The Java Platform Today
6
Stable
Secure
Free

Oracle JDK Binaries
 Oracle binaries differ from OpenJDK source
– Additional features
 Browser plugin, WebStart
– Additional tools
 Flight Recorder, Mission Control
– Some parts replaced
 Font rendering engine, colour management
– Different license
 Oracle Binary Code License (BCL), not GPLv2 with CPE
 Field-of-use restrictions
7

JDK 9 Changes Deployment
8
Modular run-time
image
…confbin
jlink
jmods
Modules

Building An Application Runtime
$ jlink --module-path $JDKMODS:$MYMODS
--addmods com.azul.app –-output myimage
$ myimage/bin/java –-list-modules
java.base@9
java.logging@9
java.sql@9
java.xml@9
com.azul.app@1.0
com.azul.zoop@1.0
com.azul.zeta@1.0

The Implications Of jlink
 "Write once, run anywhere"
– Long term Java slogan, mainly held true
 jlink generated runtime may not include all Java SE
modules
– But is still a conformant Java implementation
– To be conformant:
 It must include the java.base module
 If other modules are included, all transitive module dependencies
must also be included
– Defined as a closed implementation

JDK Development Changes

OpenJDK: New Release Model
 Time-based release model
 A new version of the JDK will be released every six months
– March and September
– Starting this year: JDK 10, JDK 11
 OpenJDK development will be more agile
– Previous target was a release every two years
 Features will be included only when ready
– Targeted for a release when feature complete
– Not targeted at specific release when started
12

JDK 9: The Clean Up Starts
 JDK 9 was a significant change for Java
– Deprecated APIs were removed for the first time
 Six methods and one class
– Redundant features eliminated
 jhat tool, JVM TI hprof agent
 Numerous deprecated GC options removed
– Unified JVM logging introduced
 Many JVM flags changed
 Some from JDK 8 will stop the JVM starting
13

Compatibility Not Guaranteed
 New versions of Java may include breaking changes
– Anything for removal will be deprecated first
– Minimum of one release warning
 Could be only six months
14

Housekeeping Will Continue
 JDK 9 deprecated some significant features
– Applets as a deployment mechanism, WebStart
– CMS garbage collector
– Java policy tool, jconsole, Doclet API, other small things
– java.se.ee meta-module
 java.corba
 java.transaction
 java.activation
 java.xml.bind
 java.xml.ws
 java.xml.ws.annotation
15

OpenJDK: More Open Source
 Oracle will open-source closed-source parts of the JDK
– Flight recorder
– Mission control
 The goal is for there to be no functional difference between
an Oracle binary and a binary built from OpenJDK source
– Targeted for completion late 2018
16

Oracle Binaries
 Until now released under Oracle Binary Code License
– Have to accept to download
– Classic "field-of-use" restriction
 Moving forward
– Binaries available under GPLv2 with CPE
– No more 32-bit binaries
– No more Arm binaries
– Windows, Linux, Mac and Solaris SPARC only
 All 64-bit
17

Availability of JDK Updates
 JDK releases now one of two types:
– Feature release
 Six months of updates
– Long term support (LTS) release
 Three years of updates
 No more overlap of updates
– Feature release to feature release
– LTS release to LTS release
– Migrating applications to new platforms must be planned
more carefully
18

Feature or LTS?
 JDK 8 has been classified as an LTS release
– Alignment means more than 3 years of updates
 JDK 9 is a feature release
– Updates only until JDK 10
 Next LTS release is JDK 11
– JDK 8 public updates stop in September this year
19

JavaSEVersion
19 19
18 18
17(LTS) 17(LTS)
16 16
15 15
14 14
13 13
12 12
11(LTS) 11(LTS)
10 10
9 9
8(LTS) 8(LTS)
Oracle Extended
Commercial Support
Oracle Commercial
Support
7(LTS) 7(LTS)
2017 2018 2019 2020 2021 2022 2023 2024
Oracle Publicly available
binaries (unsupported)
Public updates
zero overlap
(“Support Cliff”)
Java SE Life Cycle: 5+ Year Timeline

The Java Platform Soon
21
Stable
Secure
Free
Choose two out of three

Azul's Zulu Java

Zulu Java
 Azul’s binary distribution of OpenJDK
– Passes all TCK tests
– Open source licensing verified
 JDK 6, 7, 8 and 9 available
 Wider platform support:
– Intel 64-bit Windows, Linux and Mac OS X
– Intel 32-bit Windows and Linux
– Arm 32 and 64-bit
– PowerPC
23

Azul Zulu Commercial Support
 Short Term Support (STS)
– Two quarterly releases after next JDK is released
– 6 month overlap (+ 6 month passive support)
 Long Term Support (LTS)
– Longer than Oracle is offering
– All bug and security fixes back ported as necessary
– Minimum ten year support (8 active + 2 passive)
24

Azul Zulu Commercial Support
 Medium Term Support (MTS)
– Two interim, feature releases treated as production stable
– JDK 9 will be MTS (2½ years support + 1 year passive)
– JDK 11 will be starting point for future MTS releases
25
JDK 11 JDK 17
3 years 3 years
JDK 13
JDK 15
18
months

7 (LTS)
2017 2018 2019 2020
8 (LTS)
19
18
17 (LTS)
16
15
14
13
12
11 (LTS)
10
9 9
8(LTS)
7(LTS)
Azul Zulu Passive
Commercial Support
Oracle Commercial
Support
Oracle Extended
Commercial Support
Azul Zulu Active
Commercial Support
2022 2023 20242021
Oracle Publicly available
binaries (unsupported)
14
13
12
11(LTS)
10
19
18
17(LTS)
16
15
JavaSEVersion
Azul Zulu LTS Support
8 years active
Azul Zulu MTS Support
Bridge to next LTS
Azul Zulu STS Support
1 year active
Java SE Life Cycle – 5+ Year Timeline

Summary

Java Is Changing
 Faster delivery of new features
– Six month release cadence
 Two types of release
– Feature and Long Term Support
 No more overlap of updates
 Azul can help!
– Extended support available for all releases
– Ease the migration path for applications
– Tested and supported (not just porting fixes)
28

@speakjava
Thank you!
www.azul.com/products/zulu-and-zulu-enterprise
Simon Ritter
Deputy CTO, Azul Systems
29

Java Support: What's changing

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Java Support: What's changing

Similar to Java Support: What's changing (20)

More from Simon Ritter

More from Simon Ritter (17)

Recently uploaded

Recently uploaded (20)

Java Support: What's changing