Jodd – The Unbearable Lightness of Java
1–10 of 239 posts
Re: Jodd – The Unbearable Lightness of Java
#2Looks nice, and reminds me of the ecosystem around Quarkus. I have two questions:
1) Is this compatible with GraalVM? I'm mostly asking this out of curiosity.
2) Is it using "modern" Java features? Records, pattern matching, optionals.
Re: Jodd – The Unbearable Lightness of Java
#3Looks good.
Is there a "Getting Started" guide or a list of examples anywhere? I'm on mobile so may have missed them. All I could see were links to the separate component docs.
Re: Jodd – The Unbearable Lightness of Java
#4Past discussions:
Re: Jodd – The Unbearable Lightness of Java
#5I wonder if someone can recommend a lightweight http server library? I like Javalin but it's based on Jetty which is a fully JavaEE compliant framework and includes support for things like OSGI which I don't need. With the whole Log4j situation, I'm re-evaluating some the libraries I've previously relied on.
Re: Jodd – The Unbearable Lightness of Java
#6I haven't really touched Java in a while but I don't get why you'd want a lightweight DI container.
You can just build your object graph and pass dependencies manually if you want a lightweight approach, no? That's just the way people do it in most languages.
Re: Jodd – The Unbearable Lightness of Java
#7I wonder if someone can recommend a lightweight http server library? I like Javalin but it's based on Jetty which is a fully JavaEE compliant framework and includes support for things like OSGI which I don't need. With the whole Log4j situation, I'm re-evaluating some the libraries I've previously relied on.
We looked around since we wanted to move off Tomcat and decided on Netty: https://netty.io/
I'm not on the engineering team so can't speak to the cost/benefit, but it seems to have been a pretty successful transition.
Re: Jodd – The Unbearable Lightness of Java
#8I haven't really touched Java in a while but I don't get why you'd want a lightweight DI container . You can just build your object graph and pass dependencies manually if you want a lightweight approach, no? That's just the way people do it in most languages.
Agreed. Stuff like this feels like magic for magic’s sake, and as someone who has had to operate services that use these DI frameworks, they are a big pain.
Re: Jodd – The Unbearable Lightness of Java
#9I wonder if someone can recommend a lightweight http server library? I like Javalin but it's based on Jetty which is a fully JavaEE compliant framework and includes support for things like OSGI which I don't need. With the whole Log4j situation, I'm re-evaluating some the libraries I've previously relied on.
If you’re on Kotlin, consider http4k
It can use netty, undertow, and others under the hood
Re: Jodd – The Unbearable Lightness of Java
#10I wonder if someone can recommend a lightweight http server library? I like Javalin but it's based on Jetty which is a fully JavaEE compliant framework and includes support for things like OSGI which I don't need. With the whole Log4j situation, I'm re-evaluating some the libraries I've previously relied on.
We looked around since we wanted to move off Tomcat and decided on Netty: https://netty.io/ I'm not on the engineering team so can't speak to the cost/benefit, but it seems to have been a pretty successful transition.
EDIT - it seems maybe I was wrong here
Netty copies the response body when sending to each client, so it's not as lightweight as I've found. For streaming large response bodies, it does not work well. I haven't found a good Java alternative yet (probably will switch to C++ and uWS...)