spring-native VS jackson-module-kotlin

It was probably not a very good idea to write Lambda using Java programming language and Spring Boot Framework. Despite the well-spread usage and knowledge of this framework, the fact that Spring (Boot) heavily uses reflection and takes time to start the embedded Web Application Server led to very big cold starts which we'll explore in the next section. But now with SnapStart on AWS and GraalVM Native Image Support we have two more options how to optimize those cold starts. So let's explore how to write Lambda function using the Spring Boot. The code of this sample application (the same as for the first 3 parts but rewritten to use Spring Boot) can be found here. It provides AWS API Gateway and 2 Lambda functions: "CreateProduct" and "GetProductById". The products are stored in the Amazon DynamoDB. We'll use AWS Serverless Application Model (AWS SAM) for the infrastructure as a code.

During this experience, I was surprised to find that Spring Native doesn't support caching yet. I believe this support will be added by the community soon. In the meantime, if you're looking to start/stop your infra as fast as possible, you probably don't care about caching. Caching is made for long-lived, JVM-strong, JVM-loving apps.

fuente: https://spring.io/blog/2021/03/11/announcing-spring-native-beta

As I just found out thanks to a comment from another Redditor, spring-aot will be getting some functional configuration compile time generation support in Spring Native's next release

Not sure how far they are currently, but have you heard of Spring Native? https://spring.io/blog/2021/03/11/announcing-spring-native-beta

I have to say Spring. Because it is so mature and well-documented. Sure, it is bloated sometimes and not very well-suited for small JAR packages. And I have tried other frameworks as well, but I find that I keep returning to Spring. Especially since Spring keeps adding features that caused competing framework to have an edge over Spring, like native images with Spring Native for example.

Our next steps are : provide great Kotlin/JVM/Native (Native with Kotlin JVM via GraalVM native images) support via https://github.com/spring-projects-experimental/spring-native/, empowering multiplatform development (with Kotlin/JS frontend for example), translating Spring Boot documentation to Kotlin (via a contribution from Kotlin team), make sure that some APIs like WebTestClient currently broken with Kotlin due to some type inference bugs with recursive generic types become usable.

I doubt micronaut has better runtime performance. You're probably talking about startup time and this point is moot with either https://github.com/dsyer/spring-boot-auto-reflect Or https://spring.io/blog/2021/03/11/announcing-spring-native-beta

strictNullCheck option in the Kotlin module doesn't cover non-object-field situations at all. https://github.com/FasterXML/jackson-module-kotlin/issues/479

But, it sucked. I was constantly finding bugs related to nullability, around generics, inline/value classes, etc. And it wasn't the typical trivial ones, either. Figuring out that you're calling a Java library and encountering a "platform type" is the least problematic. My biggest struggle came from using libraries that were written in Java first, but then added a Kotlin API on top. So, my code didn't know I was dealing with a platform type and neither did I. Yet they were still broken. Some of them are broken in an unfixable way, such as JacksonXML's Kotlin module: https://github.com/FasterXML/jackson-module-kotlin/issues/479. So many Java libraries rely on reflection even when it's not obvious that they might, so you pretty much can't ever use value classes in Kotlin, including the unsigned number types.

You should add Jackson Module Kotlin in your project. After that, you can't specify a type of object explicitly.

Not really, you just need to handle some standard types and have a good extension mechanism to let the user implement factories. That library having built in support for UUID and datetime is probably a bit much, I'd prefer a plugin like https://github.com/FasterXML/jackson-module-kotlin

There is a bug at this very moment that makes it literally impossible to deserialize [1, 2, 3, null] into a List with Jackson's Kotlin module. Yes- even if you set KotlinModule(strictNullChecks = true). It's just broken. (Here's the link: https://github.com/FasterXML/jackson-module-kotlin/issues/479)

Got you, thanks. I didn’t mean to sound offensive - a better wording would be that they don’t seem to prioritize this part, at least based on https://github.com/FasterXML/jackson-module-kotlin/issues/199, which has one abandoned branch from a 3rd party and a couple of comments from from maintainers.

If you use Jackson, don't forget to include the Kotlin extensions https://github.com/FasterXML/jackson-module-kotlin

Did you include jackson-module-kotlin?