Using GraalVM to run Native Java in AWS Lambda with Golang

If you are deploying serverless applications in AWS Lambda and using Java, you are well aware of cold start problems. Cold start happens because of the way the Java Virtual Machine works, it kicks in JIT (Just-in-time), and it needs to “warm-up” like a car from the 80s. AWS Lambda caches containers for you, so when idle, it is paused and brought back online immediately as soon as a request arrives

[yujiorama]

GraalVMでネイティブバイナリにしたJavaを、go からJNIで呼び出し。

[mooonymann]

“Graal + Go version was always slower, but the runtime duration was more consistent. It suffered no cold start, but it also consumed more memory. Plain Java version used 50–60 MB of memory but the Graal version used additional 110–290 MB of memory.”

[braitom]

GraalVMでJavaをネイティブバイナリにしてそれをGoからJNIで呼ぶ