aws-lambda-rust-runtime

The most relevant uses of Zig that come to mind are: - Bun, as you mentioned - https://tigerbeetle.com/ - https://www.uber.com/en-IT/blog/bootstrapping-ubers-infrastr... Plus a bunch of other companies (including some very big ones) and projects that use Zig here and there, eg AWS uses cargo-zigbuild https://github.com/awslabs/aws-lambda-rust-runtime/blob/e2d5... Zig also has a few other very promising OSS projects: - https://github.com/riverwm/river (wayland compositor) - https://github.com/ZigEmbeddedGroup/microzig (HAL for embedded development) - https://machengine.org/ (truly cross-platform gamedev) - https://github.com/michal-z/zig-gamedev (another serious gamedev toolkit) Just off the top of my mind. Like for all things, you gotta get started somewhere and this is where we are at the moment.

Rust on Lambda's using containers as the deployment artifact are also very good, i'd say a perfect match. Low artifact size, low cpu+memory usage, fast execution. I think AWS must be using increasingly using Rust on Lambda internally from the talks I've seen them publish and the work gone in to https://github.com/awslabs/aws-lambda-rust-runtime. For simple REST API's there's not much extra effort in using Rust once you are familiar.

This used to be harder -- you would set the lambda up for the go language runtime, but send your own statically linked binary with a special name instead of a compiled go artifact. But now AWS offers Custom Runtimes[0]. So you can set up the infra using some convenient tool such as AWS CloudFormation templates, terraform, or ansible, and then deploy your custom runtime c/c++ build from there (again, using ansible or AWS CLI or whatever). If you're using rust, there are now ways to make that work, including plugins for the popular "serverless" (sls) framework to deploy rust builds[1] [0] https://docs.aws.amazon.com/lambda/latest/dg/runtimes-custom... [1] https://github.com/awslabs/aws-lambda-rust-runtime

Oddly, the official rust lambda runtime is not being actively maintained any more and the community is moving towards a fork by netlify [0][1] 0: https://github.com/lamedh-dev/aws-lambda-rust-runtime 1: https://github.com/awslabs/aws-lambda-rust-runtime/issues/27...

Just a minor example. https://github.com/awslabs/aws-lambda-rust-runtime/blob/mast... Could you explain to a junior what Box<dyn std::error::Error + Send + Sync + 'static> does and how should a person who is starting to learn Rust come up with something like this? Second minor example. I have a configuration string like let's say timeout for a certain type of connection. What is the recommended way to have that as a string that is accessible to all functions without fighting with the borrow checker? In Elixir, I would use @timeout in the module for example. In Rust, I am not sure. Cloning the value to every place it needs it as a workaround.

this? https://aws.amazon.com/blogs/opensource/rust-runtime-for-aws... https://github.com/awslabs/aws-lambda-rust-runtime https://crates.io/crates/lambda_runtime you rock! That docker based build system makes building those MUSL based rust binaries a snap!

As of yesterday, lambda only provided a way to specify a function handler. The input to that function, and the response value from that function, needs to be deserialized and serialized (and implicitly, construct a runtime in which the concept of a function exists). Previously, a runtime for each supported language handled deserializing the wire protocol into a runtime object, invoking the specified function, routing stdout and stderr to cloudwatch, serializing the function's return value, and transforming runtime exceptions into response exceptions. The lambda team is now letting you write that runtime, and presumably providing more documentation on the responsibilities of the runtime. Check out the example C++ and Rust runtimes to understand why each language needed to have it's own custom runtime. https://github.com/awslabs/aws-lambda-