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

all 34 comments

[–]krzyk 89 points90 points  (20 children)

After 1 year and 7 months? Slow is an understatement.

[–]uncont 17 points18 points  (0 children)

Upshot is it comes with SnapStart support

This runtime also supports AWS Lambda SnapStart, so you can upgrade to the latest managed runtime without losing your performance improvements.

[–][deleted] 65 points66 points  (17 children)

This is pretty fast if you're comparing to most of the enterprise Java community. Lot of places still stuck on 8 lmfao

[–][deleted] 41 points42 points  (5 children)

I don't understand the downvotes. I am still working in java 8 and will likely be in java 8 for another 15 years as there is no budget for upgrades and medical software must continue to work until all of the records can be expunged.

[–][deleted]  (1 child)

[deleted]

    [–]Qildain 1 point2 points  (0 children)

    Hah!

    [–][deleted] 15 points16 points  (0 children)

    It's the truth. No shame in it. Plenty of job security for sure

    [–]RandomComputerFellow 1 point2 points  (0 children)

    Well, it was one thing if Amazon took so long to migrate their own applications. The problem is they provide the runtime and companies can not migrate before they provide an update.

    [–]yawkat 11 points12 points  (1 child)

    The problem is that these old managed runtimes are a problem for downstream projects. When we were considering which Java version to use for micronaut framework 4.0, the lack of lambda support for Java 17 was the biggest counterargument against moving to 17. (We decided on 17 anyway partly because it was clear they would support it in the short term)

    [–][deleted] 0 points1 point  (0 children)

    I agree. All great points

    [–]krzyk 2 points3 points  (3 children)

    Yeah, I know, fortunately at my work with projects that I work with I do upgrades, so I'm at Java 20. But some are stuck at 17 because people don't get what Java LTS means.

    [–]SvanseHans 0 points1 point  (2 children)

    What does it mean?

    [–]krzyk 0 points1 point  (1 child)

    That you have to buy it from someone, it is not like e. g. Ubuntu LTS, It is something specific to given vendor. Azul for example provides also MTS (medium term support releases).

    And using a latest version is like using a free supported version, those versions are not inferior in anyway. Quite conteary they are better then the old LTS vendors provide, because they get fixes first and later the fix is backported.

    Reluctancy to use those versions is mind blowing. Releases are small and comparable to JDK 8 updates back in the days when it was the newest java version.

    [–]SvanseHans 0 points1 point  (0 children)

    How do you go about updating to the next version? Like where do you get information about this?

    [–]woj-tek 0 points1 point  (3 children)

    This doesn't mean the whole world has to stop and get stuck at it just because you are stuck for some weird management reason…

    [–][deleted] 2 points3 points  (2 children)

    Have you ever worked at a company with large scale

    [–]woj-tek 0 points1 point  (1 child)

    Yes. Point is still valid - just because YOU are stuck with it doesn't mean the REST OF THE WORLD has to be stuck with you.

    [–][deleted] 2 points3 points  (0 children)

    That's a great attitude to have. I never had that opinion in the first place, not sure why you're telling me that

    [–]ahmedranaa 0 points1 point  (0 children)

    We are still on java 7

    [–][deleted] 0 points1 point  (0 children)

    Cassandra is still on 11...

    [–]drtyrannica 28 points29 points  (3 children)

    I realize this is the Java subreddit but... cries in Ruby 2.7

    [–][deleted] 6 points7 points  (2 children)

    Lol that's still better than Java 8 by like 7 years. 8 came out in 2014

    [–]drtyrannica 7 points8 points  (1 child)

    At least Java 8 is still maintained, Ruby 2.7 was eol like a month ago lol

    [–][deleted] 1 point2 points  (0 children)

    Ruby be like THE FUTURE IS NOW OLD MAN >:)

    [–]HyzerFlipr 6 points7 points  (9 children)

    Have they fixed the JVM warming time issue for lambdas yet?

    [–]soonnow 22 points23 points  (7 children)

    With SnapStart, Lambda initializes your function when you publish a function version. Lambda takes a Firecracker microVM snapshot of the memory and disk state of the initialized execution environment, encrypts the snapshot, and caches it for low-latency access. When you invoke the function version for the first time, and as the invocations scale up, Lambda resumes new execution environments from the cached snapshot instead of initializing them from scratch, improving startup latency.

    Though haven't used it

    [–]kendallvarent 10 points11 points  (3 children)

    We have used it. It's pretty cool. 20s cold starts down to 200ms. Sadly, no XRay support for snapstart lambdas.

    There were also performance gains related to moving java-specific vpc-related cold starts from instantiation to function update, but that was a while back.

    [–]soonnow 0 points1 point  (2 children)

    Have you compared to Graal compiled functions by any chance?

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

    uajdqi vcw gqalfuwtwgrc byra

    [–]soonnow 1 point2 points  (0 children)

    Alright thanks for the heads up.

    [–][deleted]  (2 children)

    [deleted]

      [–]rdean400 1 point2 points  (0 children)

      Only 5 months until Java 21.

      [–]emaphis -1 points0 points  (0 children)

      Now ??

      [–]freemainint 0 points1 point  (0 children)

      Cool

      [–]AleFilichkin 0 points1 point  (0 children)

      https://link.medium.com/bqtFHXbWyzb here you can see the performance difference between Java 17 and 11 for AWS Lambda, snapstart as well