I’d like to formulate a plan for having Akka offer out of the box support for Graal’s native-image tool. I fear that Akka will be left behind as other toolkits and frameworks gain such support.
Native image generation is not only important for fast startup, but also for reduced memory consumption. My tests of Graal’s native image tooling have shown a simple hello world app reduces its resident memory size by a factor of 10. Reducing resident memory has a positive impact on a business given reduced operating costs i.e. there are less machines required to run a system.
Outside of the JVM, using Graal’s native image tool can present Akka based services that compete with Go on all fronts. Go is fast becoming an alternative to using the JVM for microservices, particularly because of its focus on resource usage.
My initial experiments with Graal and Akka resulted in finding a Graal issue in rc1 (1). The Graal team haven’t been focused on Akka and I think that it is up to us, the Akka community, to bring Akka to their attention.
I’ve previously attempted to raise the subject of reduced resident memory usage for Akka, and got a lukewarm response (2). My former colleagues at Lightbend may recall me harping on the importance of addressing JVM resident memory usage over the years. My Landlord project was even formed to tackle this problem head on (3). Now that Graal is real, I’d like to test the water again and gauge whether any efforts in formulating a plan to tackle Akka and Graal’s native image support would be warmly received.
Thanks for reading this far. In summary, is there an interest in a pursuit of Akka for Graal’s native image tool?