this post was submitted on 30 Sep 2023
101 points (91.1% liked)

Programming

17526 readers
278 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] AstridWipenaugh@lemmy.world 2 points 1 year ago (1 children)

I don't recall which Java environment was used; I'm not a Java developer so some of those technical details went in one ear and right out the other. They did implement snapstart for Java lambdas and that made the warm start time similar to Go. But the runtime performance isn't even close after they put a bunch of effort into trying to optimize it.

I truly can't recommend anything other than Go for lambdas. It's better by every metric and it's a lot easier to manage your infrastructure (just a single binary file with no file or environmental dependencies; it doesn't get any more straightforward than that.) I'd definitely recommend doing a PoC to compare performance for your specific workload in Java vs. Go. As long as you have devs capable of writing Go, it's a real winner. If you don't, I'd still go with nodejs lambdas over Java; Java still seems to require a lot of tweaking to get its performance comparable. It's a 30 year old swiss army knife, and it shows.

[โ€“] kassuro@feddit.de 2 points 1 year ago* (last edited 1 year ago)

Thanks for your answer.

It's a 30 year old swiss army knife, and it shows.

There is a lot of improvementsn happening in the Java space , so that might change over the next years.

It's better by every metric and it's a lot easier to manage your infrastructure (just a single binary file with no file or environmental dependencies; it doesn't get any more straightforward than that.)

With these new native builds you also get a single binary file as far as I know ( I'm still kinda new to Java) and much better startup times. So today Java might perform a little better in this comparison.

But I take it as a good chance for getting a chance to introduce go as a language.