Node.js 24 runtime is available on AWS Lambda from 25th November 2025. It removes support for callback-based function handlers. In this article I will go through things which you should know before you upgrade your runtime.
First of all, a big shout out to Martin Damovsky for providing re:Watch service where you can rewatch all the sessions from re:Invent 2025.
Two weeks ago I've published Lambda Bun Runtime and Lambda Keep Active CDK constructs which you can download and install from npm. I've also written about those in their respective articles.
Since there is strong community build around Constructs Hub I wanted my constructs to be available there as well. Unfortunatelly for me you need to use projen in order to be picked up by Construct Hub. So I have converted my repositories to projen repositories. This article is about my thorny path.
Let's do one more digest before the madness named AWS re:Invent starts as I think once it is over I will be curating one special digest for all of new AWS releases which I find interesting.
Last Thursday I have attended CodeCon in Žilina. There were various great presentation but one of them stick with me. Fero Volár was talking about his experience with leadership and he mentioned how you can use Talent Dynamics test to build great teams.
He also mentioned how you can complete the questionnaire by asking ChatGTP without actually buying the questionnaire. Of course, I have tested this and it was really interesting.
What is Bun and why you should use it? Also everything is more fun with AWS Lambda, right?
In this short article you will learn what does it mean when your Lambda transitions to inactive state and how to deal with it.
You can use our CDK construct @beesolve/lambda-keep-active which invokes your Lambda functions regularly so they won't transition into inactive state.
I've just spend 30+ minutes setting up DS record in local webhosting provider. The reason? Lack of coffe or maybe bad UX. Or maybe both.
When people compare things like on-prem vs cloud or vps vs serverless they tend to compare just the initial cost and the running cost. Very few people I've met are fully aware of things like maintenance cost, hardware deprecation, flexibility, scaling and all the hidden costs which you only find out after a few months/years of running your service online.
Each solution has it's fit, you just need to know the distinction. For me it goes like this:
Recently I've been talking to people on various meetups about the Serverless technology and I noticed pattern - lot of people think about serverless as limitation rather than solution to real problems.
I've decided to bust a few myths I've been hearing repeatedly lately regarding the whole Serverless ecosystem. I am going to focus on AWS serverless technologies not serverless technology in general.