How Does New Oracle JVM Licensing Encourage Agility

How Oracle pushes companies to be more agile by shortening release cycle.

Oct 23, 2018 2 minutes read

What happened?

Oracle has changed release and licensing policy for JDK:

  • The JDK still remains completely free for use. The thing that is changing is the availability of updates to specific versions of the JDK.
  • The only free for use in production JDK binary available from Oracle (as of JDK 11) will be the OpenJDK binaries. These will only have public security patch and bug fix updates for six months, until the release of the next version.
  • There is no free LTS release of the JDK from Oracle (for use in production).
  • Users can continue to use any binary of the JDK (the Oracle version or OpenJDK one) indefinitely. They will not, however, continue to get updates to these JDKs once public updates end.
  • Commercial users who want to continue to get security patches and bug fixes for JDK 8 or subsequent LTS releases after public updates have ended will have three options:
    1. Purchase a commercial support contract from Oracle.
    2. Use a different binary distribution of the OpenJDK, which has security patches and bug fixes backported to it.
    3. Create their own binary distribution from the OpenJDK source code and backport updates themselves.

How does it encourage agility?

  • Most of the companies are not willing to purchase commercial support from Oracle.
  • At the same time, they need to get latest security updates.

So, what companies have to do –- is to upgrade JDK on production environments more frequently: at least every 6 months.

It means, that companies has to re-test and re-deploy their applications at least every 6 months, after each JDK update. Important step here is testing. Regression testing. Oracle pushes companies to spend more efforts in test automation so rolling out updates would be cheaper. Running regression tests is easier than manual testing.

Having more test automation brings the industry close to wider adoption of CI/CD. It shortens release cycles and, eventually, time-to-market. Companies may take advantage of it by shortening product feedback cycle and rapidly adapting to market changes.

IMHO, two weeks is the maximum acceptable release cycle. With longer cycle, Customers will start feeling themselves detached from the product.

See Also

The Typical Mistake in Web-Service Design

Working on different projects I often see the same problems with application design.

UI-First Development

One of the challenge for start-up or any new project is to reduce amount of work yet to deliver full-featured product. Agile methodologies address this challenge on project management level. Let’s discuss one more approach to address it on architecture level: UI-first development.

logo   Never miss a story, subscribe to our newsletter