Spring Native has availability on start.spring.io, In practice, that means that in addition to the regular Java Virtual Machine supported by Spring since its inception, support for compiling Spring applications to native images with GraalVM has offered to provide a new way to deploy Spring applications. Of course, Java and Kotlin are supported.
Those native Spring applications can be deployed as a standalone executable (no JVM installation required) and offer interesting characteristics including almost instant startup (typically < 100ms), instant peak performance, and lower memory consumption at the cost of longer build times and fewer runtime optimizations than the JVM.
For RocketMQ Spring, we should do the following things:
- Native Netty for less image
- Native RocketMQ SDK for less image
- Adapte to the latest stable spring native dependencies[1]
@snicoll how do you think about the spring native support for some popular existing SDK :-)
[1] https://github.com/spring-projects-experimental/spring-native
Spring Native has availability on start.spring.io, In practice, that means that in addition to the regular Java Virtual Machine supported by Spring since its inception, support for compiling Spring applications to native images with GraalVM has offered to provide a new way to deploy Spring applications. Of course, Java and Kotlin are supported.
Those native Spring applications can be deployed as a standalone executable (no JVM installation required) and offer interesting characteristics including almost instant startup (typically < 100ms), instant peak performance, and lower memory consumption at the cost of longer build times and fewer runtime optimizations than the JVM.
For RocketMQ Spring, we should do the following things:
@snicoll how do you think about the spring native support for some popular existing SDK :-)
[1] https://github.com/spring-projects-experimental/spring-native