So I hope I can upgrade soon my AWS lambda functions also to Node 22. More on github.com

I'd recommend looking into CDK for a way of writing infrastructure as code. This is built by Amazon and is essentially a 1 to 1 mapping to Cloud formation templates. For a more abstracted approach, check out SST but this is still in its early days, especially V3. For production you should never be managing infrastructure directly through the console, and should instead use an infrastructure as code tool with a cli to update your deployed infrastructure automatically. YouTube is a good resource too: Serverless Land FooBar Serverless More on reddit.com

the error is pretty clear to me. for one of those records, the pk is not a string. it’s an object. the problem is that this error is a little ambiguous in terms of where it’s coming from. i tend to lean towards, aws isn’t the issue and that would encourage me to look at my input data and make sure it’s actually as i expect. additionally, i would consider putting a queue in front of the ddb insert so that you can catch and redrive failed records or triage the reason for failure. although i don’t blame aws they do fail sometimes and a dead letter queue helps that. plus it’s good practice for reducing write density issues More on reddit.com

That’s not really unique to Node. The majority of languages and web app platforms have concurrency mechanisms that will process multiple requests simultaneously. That is certainly a drawback of Lambda if you’re looking at raw CPU cycle efficiency and your application spends a lot of time waiting on synchronous downstream calls, but in most cases that doesn’t really matter. In practice, there are a lot of apps that can either use really fast data stores like Dynamo or use asynchronous processing models that minimize the amount of idle CPU time for a given request. Also, even with some inefficiencies when looking at high concurrency time periods, sometimes the ability for Lambda to immediately scale down during troughs in your load pattern makes up for it when looking at the global efficiency of the system (especially when you consider other operational overhead like patching servers.) Bottom line, people use Node with Lambda because they like the language and are familiar with it. Using the same language for the front end browser code and the backend is nice for teams that build full stack web apps. More on reddit.com