graalvm 2025-10-20

GraalVM native-image application layer demo: https://github.com/graalvm/graalvm-demos/tree/master/native-image/microservices/micronaut-hello-rest-maven-layered The base layer is a dynamic library, the final layer an application using the base layer as a library

In the case of Babashka, this could be an alternative for pods or something else?

i didn’t know this was real, i thought it was still years out

Initially I hoped so, but if the base layer is a dynamic library then it won't work since the base layer should be babashka, an application

🤔 1

Reading https://github.com/oracle/graal/blob/master/substratevm/src/com.oracle.svm.core/src/com/oracle/svm/core/imagelayer/NativeImageLayers.md#native-image-layers-architecture maybe it would be possible to publish babashka and pod layers and then it would relatively cheap to recombine it into a custom babashka runtimes enabling native extensions like pods. Not sure if that is very interesting and of course assuming I understood the architecture correctly

hmm, I didn't read that far. ah good. yeah maybe that'll work. but users would still need to use native-image to use a pod then, which is kind of inconvenient. might as well use the existing features flags then

Yeah it doesn't sound like a big win for this use case

I hoped it would