LLRT is basically no learning curve. Same old esbuild most TS and JS devs are used to. I guess we're sticking with one language from front to back again:
CDK in TS, lambdas in TS, and frontend logic in TS.
LLRT is basically no learning curve. Same old esbuild most TS and JS devs are used to. I guess we're sticking with one language from front to back again:
CDK in TS, lambdas in TS, and frontend logic in TS.
In fairness I would rather pick Go, C# with Native AOT, or Java with GraalVM, if Rust build times are such a pain point.
Keep the performance of compiled languages, with faster build times, no need to switch to a bare bones interpreter.
Native AOT OTOH has first-party support and is the recommended deployment target: https://docs.aws.amazon.com/lambda/latest/dg/dotnet-native-a...
(fun fact: AWS beat Azure to it with its support)
LLRT gives the quick dev and deployment time, automatic OS and SDK updates (when using a zip rather than Docker image), and very low cold start latencies. The rest is nothing much more than await-ing network responses.
Obviously if it were calculating millions of hashes, rendering images, and other similar tasks, I'd run to Rust or Go. But the default looks to be LLRT.
Any larger program with thousands of lines of code or more wouldn't be in TypeScript. But for a twenty-line lambda, especially with JSDoc that has no separate build step? No brainer for me in terms of cost-benefit.