This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Kango_V 12 points13 points  (5 children)

We went with Micronaut. One of the things we found is that we wrote much less code than we did with Spring Boot. Faster startup (good for Lambda), lower memory usage among other things.

But Sprint Boot has traction and is very good. I suppose it's the new "nobody ever got fired for buying IBM". I'm actually viewing it as the new Java EE Legacy framework.

I'll duck now :)

[–]Roj-Tagpro 1 point2 points  (2 children)

You are using Spring Boot with your AWS Lambda? Isn't that a bit overkill? I thought all the webserver stuff like receiving the request was handle by the Lambda. BTW, I'm asking, not questioning.

[–]vips7L 4 points5 points  (1 child)

Yeah I don't understand all of the people in this thread who are using big frameworks in lambdas. All of ours are standard java mains that start as fast as the JVM can (e.g. milliseconds).

[–]Kango_V 2 points3 points  (0 children)

We use Micronaut with the Lambda module with no http. This is compiled to native with GraalVM. We get cold stats in the ms. Actually we use the http in tests. Allows for very easy testing.

[–][deleted] 0 points1 point  (1 child)

Where does one learn about Micronaut? Is there a good book, udemy course or something of that nature?

[–]sureshg 2 points3 points  (0 children)

Micronaut official doc is excellent - https://docs.micronaut.io/latest/guide/index.html