4 ms·
I guess Quarkus and Spring 3 native are meant for bringing existing apps to serverless deployments and fast startup times (plus process-level isolation as an op
by tannhaeuser 2y ago
I guess Quarkus and Spring 3 native are meant for bringing existing apps to serverless deployments and fast startup times (plus process-level isolation as an option?), but it's true there are also new apps being developed using Quarkus. The investment in tooling, inertia of the ecosystem of third-party libs, and predominance of traditional JIT over AOT deployments must be the reason why they're not just doing away with Spring's reflection in the first place.
- sgammon 2y agoMicronaut is essentially Spring anyway, but with build-time codegen instead of classpath scanning and runtime annotation processing. It even has a compat layer, and like Quarkus it supports GraalVM out of the box, with minimal reflection at runtime. https://micronaut-projects.github.io/micronaut-spring/5.9.0/guide/ https://micronaut-projects.github.io/micronaut-spring/5.9.0/...