I'm trying to shorten the time from a code change to a running service in a remote Kubernetes dev cluster. Building an AOT cache on every change could cost more time than it saves at startup.
Most dependencies change less often than our application code. Could a cache trained on just those dependencies be reused when the app changes?
8c~parcelspoke_419:
It would be worth checking the cache compatibility rules for the JDK version you're using before building the workflow around this.