Microsoft Build of OpenJDK

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.

Microsoft has contributed to the OpenJDK project and has also been able to develop support for the Mac M1 chipset. This is amazing that they've seen the importance of supporting all silicon in the spirit of Java. This is very commendable from the tech titan and we look forward to more improvements and enhancements.

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.

I think of a few areas when looking at Microsoft Build of OpenJDK. The first is what is your cost to run for your intended product or project, if you are strapped and fall within the supported areas of Microsoft Build of OpenJDK then it's a no brainer, Microsoft Build of OpenJDK is for you! Lastly, I think of support in the respect to running into a wall and needing a fix. It can take a while for open source tools to produce fixes that the community warrants, so again if you aren't strapped for time and haven't run into a wall and could afford to wait for fixes or relevant patches then again Microsoft Build of OpenJDK is for you. Not everyone has this luxury, but these are a few areas to think about.