Interesting! I wasn’t aware such a library/framework existed.

AWS has also removed a log4j patch from the Java 25 runtime to restore optimal performance. This was implemented when Log4shell hit the industry and was in all previous runtimes.

Starting with Java 25, Lambda no longer stops tiered compilation at C1 for SnapStart and Provisioned Concurrency.

If you deploy Java 25 functions using container images, you can either implement your own AOT caches or continue using CDS.

Lambda’s benchmarking results show that AOT caches deliver faster cold start performance compared to CDS. 🚀 AOT caches are now enabled by default in the Java 25 runtime to provide performance benefits.

AWS Lambda replaces the traditional Class Data Sharing (CDS) with ahead-of-time (AOT) caches. This is an advanced optimization feature from Project Leyden that is designed to improve application startup times and reduce memory footprint.

There is a lot to unpack from this release though. It’s not just a runtime update.

Thanks! 🙏

Likewise!

Ah yes I misunderstood. I expect the same that people are misreporting.

Not sure what that graph is based on though. I don't see any issues when looking at the Azure status page. It might be lagging behind off course. azure.status.microsoft/en-gb/status

Yeah I had the same feeling and figured the same 😅

Yes that was a late one! I think it was around 6 or 7pm or so Vegas time

Yeah I know. Last time I was in Vegas though. Time wise it would have been much better if it was around 15:30 Vegas time like this year. Especially with all the long days and jet lag 😀

Final talk of the day was an interesting perspective on evolutionary architecture with Selcuk Sasoglu - “Why Modular Monolith is a great starting architecture for a Serverless application?”