TrustRadius: an HG Insights company

Microsoft Build of OpenJDK

Score7.8 out of 10

7 Reviews and Ratings

What is Microsoft Build of OpenJDK?

The Microsoft Build of OpenJDK is a no-cost distribution of OpenJDK that's open source and available for free for anyone to deploy anywhere. It includes Long-Term Support (LTS) binaries for Java 11 and Java 17 on x64 server and desktop environments on macOS, Linux, and Windows, AArch64/ARM64 on Linux and Windows, binaries for macOS on Apple Silicon (AArch64/M1), and musl libc compiled binaries for Alpine Linux on x64.

Categories & Use Cases

Great free open source Open JDK alternative!

Use Cases and Deployment Scope

Primarily the use case was to help drive low cost development for workloads in creating cloud based digital prouducts. Microsoft Build OpenJDK allows for support of Java 17 library for use in deployed Linux environments for us to package.

Pros

  • Support for the Java libraries that are common use today
  • Support for various architecture environments - Mac, Windows, Linux, etc...
  • Provides a low cost or rather no cost alternative

Cons

  • Since it's open source, enterprise support is less than as if you are running paid like an Oracle JDK.
  • Performance is improving and is I would say on par with paid solutions, this could improve to help with growth.
  • Stability will happen over time with more contributions and fixes

Return on Investment

  • No cost alternative to paid JDK platforms
  • Performance is that of paid JDK platforms in my opinion
  • Community contribution is a bonus for contributed code and open collaboration

Other Software Used

Microsoft 365, Microsoft Azure, Azure Bot Service (Microsoft Bot Framework), Azure Application Gateway

Expected OpenJDK Behavior with Support from Microsoft

Use Cases and Deployment Scope

With so many builds of Java it is good to have a team backing and supporting your Java runtime in production. By leveraging a large company with a support relationship - from a business perspective this mitigates any risk associated with the use of a library in production. This is currently being used via Azure.

Pros

  • Support
  • Standard Implementations
  • Risk Mitigation

Cons

  • IntelliJ Support

Return on Investment

  • Consistent Support