Skip to content

Update amazon-lambda.mdx #148

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 27, 2025
Merged

Update amazon-lambda.mdx #148

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pages/edge/vs/amazon-lambda.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,4 +19,4 @@ Wasmer Edge and Amazon Lambda differ in significant ways:
- Wasmer Edge **doesn't require code changes in your application** to run, while you need to adapt your code to use the custom Lambda SDK to run.
- Wasmer Edge **lets you reuse the same architecture to deploy your static assets and your dynamic websites**, while Amazon Lambda focuses only on the dynamic requests and recommends using S3 for your static assets.
- Wasmer Edge can run UDP and other protocols while Amazon Lambda can not.
- Amazon Lambda has currently has more trigger options than Wasmer Edge
- Amazon Lambda currently has more trigger options than Wasmer Edge