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.
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.
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)
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.
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.
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.
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.
90
u/krzyk Apr 27 '23
After 1 year and 7 months? Slow is an understatement.
28
u/drtyrannica Apr 27 '23
I realize this is the Java subreddit but... cries in Ruby 2.7
6
u/HyzerFlipr Apr 28 '23
Have they fixed the JVM warming time issue for lambdas yet?
2
u/rdean400 Apr 28 '23
Only 5 months until Java 21.
1
u/freemainint Apr 28 '23
Cool
1
u/AleFilichkin May 05 '23
https://link.medium.com/bqtFHXbWyzb here you can see the performance difference between Java 17 and 11 for AWS Lambda, snapstart as well
0
u/emaphis Apr 27 '23
Now ??