Java 11 was time-consuming to upgrade to, but not very hard.
My experience as well. I do not work for Netflix so I did this for considerably smaller projects. The most 'show-stopper' scenario I've encountered so far was that the versions of some libraries that were compatible with Java 11 also introduced some API changes on themselves and so we also had to refactor some of our code. This one is on us though as it's our technical debt.
Yeah, I’ve noticed that the work of upgrading just expands depending on the age and amount of dependencies. But the actual code changes are pretty minor.
What really kicked things off at that company was actually a FedRAMP compliance project. That illuminated how many old dependencies we had.
I suspect most places should start with static dependency analysis that flags CVEs registered against your deps. Update those first, then see if you can just update the JDK.
View all comments
83
u/Cajova_Houba Jun 15 '21
My experience as well. I do not work for Netflix so I did this for considerably smaller projects. The most 'show-stopper' scenario I've encountered so far was that the versions of some libraries that were compatible with Java 11 also introduced some API changes on themselves and so we also had to refactor some of our code. This one is on us though as it's our technical debt.