powertools-lambda-typescript VS deno-lambda

The Powertools GitHub repository offers nice examples to integrate and learn from. For example here are nice example written in AWS CDK. Following I will list the features I gained some experience with.

Lambda Powertools TypeScript can't be used directly as an ES Modules dependency, but there is an issue open, so please consider adding your +1. For now, it's possible to get by with a require shim or via cjs tricks but it would be great to see native support for ES Modules in Lambda Powertools TypeScript.

for secrets, I would recommend using AWS PowerTools if you can (depending on your language) - https://github.com/awslabs/aws-lambda-powertools-python - https://github.com/awslabs/aws-lambda-powertools-typescript

The documentation for Lambda Powertools TypeScript is pretty good and provides several examples with even more on GitHub.

Last week, AWS announced the beta release of AWS Lambda Powertools Typescript. This is a suite of TypeScript utilities for AWS Lambda functions to enable the adoption of best practices in areas such as structured logging, tracing and custom metrics.

Using Deno with AWS Lambda functions requires a custom runtime. You can build your own runtime or use one that already exists. If you’re concerned about security, I suggest maintaining a copy of an existing runtime and carefully inspecting updates or creating your own runtime. For this proof of concept, I deployed the Serverless Application Repository (SAR) app for Deno into my AWS account. I used the included Lambda layer and the provided.al2 Lambda runtime to create my Deno Lambda function. I created a file called index.ts with some basic JavaScript code that makes requests to two different websites and returns the HTTP status code of the response or a caught error. I then updated the function’s configuration to reference the exported handler function.

I'm doing a simple PoC / testing with Deno using https://github.com/hayd/deno-lambda and specifically the CDK instructions.

As I had mentioned, it requires using a Lambda Layer. See: https://github.com/hayd/deno-lambda/blob/2d90756a0f18b57f16e...

Using your own image (i.e. without using the base AWS image with the layer) you'd get even worse cold start times.

Decorators and TypeScript aren't supported out of the box in Lambda (without using deno) so we'll also need a transpilation step if we go this route. Fortunately this is a mostly solved problem for AWS CDK, AWS SAM and Serverless Framework users. If you want or need to roll your own, esbuild is a great place to start and seems to be the bundler of choice for this purpose.

In addition to the stuff posted here, there's the deno-lambda project for deploying to AWS Lambda

Cloud hosting support. Deno runs fine in a container, but lambda/cloud function support is difficult on most providers. deno-lambda exists but it only applies to AWS and can't be used with all CICD tools. Deno Deploy also exists but it's pretty new.