Transitioning to Java 17 from 11 or 8 for Admins

Track: Java Platform
Abstract
If you're responsible for deploying Java-based apps (as an admin or developer), you know that transitioning to a new major Java version can be painful--or you may at least fear it will be, so perhaps you/your org have dragged your feet. But new versions can also bring important benefits. While you can readily find resources discussing Java LANGUAGE and architecture changes between the LTS (and non-LTS) versions, sometimes it's hard for an admin or maintenance dev to sort through what matters for them (who won't be "touching" code): which JVM changes are inherent vs optional, which may break or impact how code/apps perform, which may improve things, and so on. This session will look at key changes of this sort for those moving to Java 17, whether from Java 11 or 8.
Charlie Arehart
A veteran troubleshooter who's worked in enterprise IT for more than three decades, Charlie Arehart (@carehart) is a longtime community contributor who as an independent consultant provides short-term, remote, on-demand troubleshooting/tuning assistance for organizations of all sizes and experience levels.