WebAssembly on Amazon Lambda: Lessons Learned

&gt; We built a social network for pets. [...] Every story update is appended in a homemade &quot;blockchain&quot; running in WebAssembly in the Lambda worker.<p>Dear God.

Wasm. Wasm everywhere.<p>It’s going to be in your cdn edge node.<p>It’s going to be your serverless target.<p>It’s going to be your database transaction.<p>It’s going to be your device driver.<p>It’s going to be your interrupt.<p>Maybe it’ll be your native language. WAT is clunky but can easily made productive with some syntactic sugar.<p>Finally it may become your hardware target. Abstract machine no more.

FWIW, Lambda has added support for Docker images, which can run anything. They’re not limited to 500 MB either. You just have to use one of Amazon’s base images that come with the Lambda runtime installed, or add it to your existing Dockerfile. This might be the way to go for running something like Wasmer.

Very interesting!<p>Note lambdas now can have urls if you want to set that up without setting up API Gateway<p>Looks like the other rough edges are from being understandably overwhelmed by AWS. Would love to chat with the author of this article about how we can make WASM an option in SST (<a href="https:&#x2F;&#x2F;sst.dev" rel="nofollow">https:&#x2F;&#x2F;sst.dev</a>) so this is becomes a much easier option

Why use Wasm on lambda, when you could just compile your app natively?

Severless.com framework has lots of plugins that allow local emulation of AWS services like S3, dynamodb, rds, etc. that your application will be using. It also helps with running debugging remote lambdas and deploying them. There&#x27;s also SAM.<p>If you are going serverless, one of these toolkits makes it a lot easier.