The close to 'native' Python performance looks promising!
Just want to point out that this section avoids mentioning the best way to do it:
> AWS Lambda doesn't natively run unmodified Python apps:
>
> - You need adapters (such as https://github.com/slank/awsgi or https://github.com/Kludex/mangum) for running your WSGI sites.
> - WebSockets are unsupported.
> - Setup is complex, adapters are often unmaintained.
AWS provides https://github.com/awslabs/aws-lambda-web-adapter which is a) supported and b) written Rust, providing a translation of Lambda requests back into HTTP so you can use your usual entry point to the WSGI app. It is simple to set up.
WebSockets still not supported of course, but the issue of adapters is solved.
However it's worth point that due to the concurrency model of AWS Lambda (1 client request / ws message = 1 lambda invocation / one process only ever handles one request at a time before it can handle the next one), you would end up spawning much more AWS Lambda instances than you would with Cloudflare workers or Wasmer Edge.
There are cost implications obviously, but AWS lambda works this way also to make concurrency and scaling "simpler" by providing an easier mental model. Though much more expensive in theory
Just want to point out that this section avoids mentioning the best way to do it:
AWS provides https://github.com/awslabs/aws-lambda-web-adapter which is a) supported and b) written Rust, providing a translation of Lambda requests back into HTTP so you can use your usual entry point to the WSGI app. It is simple to set up.WebSockets still not supported of course, but the issue of adapters is solved.