Amazon Corretto JDK
The best way to understand which JDK to use is to understand superficially what is involved with the source code and the build process between vendors, and their licenses.<p>Source code starts out the exact same, that&#x27;s why they are all OpenJDK, because they take the source code from the OpenJDK public repository&#x27;s main branch.<p>From that point on, they can choose to apply source code patches from OpenJDK that have not yet been merged into the main branch, or they could apply their own source code patches. Those patches often will be security fixes, or backported features. Here you have to understand that there is only one main branch of Java. So if you want security fixes or new features but are still on say Java 8, someone has to pull the old commit that was tagged Java 8 and selectively cherry pick a bunch of commits afterwards to apply over it that retrofits all security fixes and possibly a few select new features (like say some performance improvements patches). And if you&#x27;ve ever had to do a cherry pick merge on old code, you know it can be tricky and sometimes there are conflicts and maybe you even need to manually resolve them.<p>And even if they are not grabbing the source from an older tagged version commit, but are grabbing it from the latest tagged commit (so as of this writing Java 17), well it might already be that there are some newer commits that fixed some security bug, or other bug, or improved performance or startup, etc. So in their build of Java 17 they could even decide to apply some of those patches that happened after to the Java 17 latest release. And they might even choose to apply some patches that haven&#x27;t even made it to the main branch yet, so maybe still have an open PR, or they are the ones patching something of their own.<p>After having grabbed the main source of OpenJDK, and potentially applied some patches to it, they proceed to build it for one or more platforms.<p>In the process of building, they will choose which platform to build for, such as Windows, Linux, MacOS, x64, ARM64, x86, etc. And they will choose what to include in the build, for example should you bundle Java Mission Control, javafxpackager, jarsigner, jstatd, visualvm, etc.<p>Finally they can choose to tests each build on each platform they built it for by running the full test suites, but they could also only partially test, as in, run only a subset of the tests, or tests only a subset of the platforms they built it for.<p>You&#x27;d want to run tests especially if you did patch the source, to make sure none of your patches introduced bugs, but the build could also have created an issue which tests could uncover, like forgotten to include some important C lib, or resource, or built with wrong optimization options, etc.<p>And last but not least, the license they choose. There&#x27;s two parts here, the first one is that if they made any changes to the source of their own, their changes might be on their own license, or might not even be open source. That means you might not be able to fork the exact source they used for your own needs, or even get to see the full source they used. The second are the terms of use for each things bundled in the build. Do they let you use the JRE for cloud applications? Can you redistribute it to others? Can you use it for commercial work, etc.<p>Hopefully that better equips you to understand. Most of the companies who make money by building OpenJDK and offering support will probably do a good job at making sure that they backport security fixes as soon as possible, and make sure to always test everything to be sure their backport and custom patches didn&#x27;t break anything, but they might not always do so for your chosen platform. But as any company who wants to make money, they need to have some of their customers pay them at some point, and that&#x27;s where licensing and terms of use come in, but more and more they go full open source on their source patches and customization, allow anyone to use things for free in all settings, but offer paid support, though to be sure read their license and terms of use.<p>And if you can&#x27;t be bothered to read their license or terms of use, that&#x27;s why people have been recommending AdoptOpenJDK which is now Eclipse Adoptium. Since they&#x27;re a community effort managed by a non-profit, you can be more confident that their license and terms will be and remain fully open source and free to use in all cases. The downside is that it&#x27;s a community effort, you don&#x27;t know if they&#x27;ll apply security patches quickly, or fully test, etc. And if there&#x27;s any issue with the build you encounter, there&#x27;s no real support, no SLA for it, etc.<p>P.S.: There also exists some alternate JDKs, that are not based from the OpenJDK&#x27;s main source branch, such as OpenJ9, GraalVM, Zing, JamaicaVM, etc. Those should be considered as alternate implementation of Java, they often have very different runtimes and garbage collector and all that, though they can still partially be using some of the stuff from the OpenJDK as well. While all the OpenJDK builds I was talking before always implement everything using the OpenJDK source, all they&#x27;d do is add security fixes, bug fixes, retrofit some newer features into older releases, etc. They wouldn&#x27;t provide alternate implementation of anything the way that GraalVM or OpenJ9, et all, will do.