Improved docs

wasmerio · Oct 5, 2023 · 55a3aa4 · 55a3aa4
1 parent 851bda0
commit 55a3aa4
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 8 deletions.
diff --git a/pages/edge/vs/amazon-lambda.mdx b/pages/edge/vs/amazon-lambda.mdx
@@ -6,13 +6,17 @@ Wasmer Edge and Amazon Lambda are both serverless platforms for running websites
 
 Wasmer Edge and Amazon Lambda share these similarities:
 
-- **Affordable**
+- **Fast startup times**
 - **Infinitely scalable**
+- Both can run as **idempotent** functions (e.g. [_WCGI_](/runtime/runners/wcgi))
 
-### Differences
+### Differentiators
 
 Wasmer Edge and Amazon Lambda differ in significant ways:
 
+- Wasmer Edge is more afforable than Lamda
+- Wasmer Edge is built on simpler and more scalable technology than Lambda (which is built on top of Firecracker)
 - 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 allow any incoming TCP connection**, while Amazon Lambda is only oriented towards HTTP workloads
+- Wasmer Edge can run UDP and other protocols while Amazon Lambda can not.
+- Amazon Lambda has currently has more trigger options than Wasmer Edge
diff --git a/pages/edge/vs/cloudflare-workers.mdx b/pages/edge/vs/cloudflare-workers.mdx
@@ -6,15 +6,16 @@ Wasmer Edge and Cloudflare Workers are both serverless platforms for running web
 
 Wasmer Edge and Cloudflare Workers share these similarities:
 
-- **Affordable**
-- **Infinitely scalable**
+- **Affordable and cheaper than traditional clouds
+- **Fully stateless** modern architecture
+- Built on a *shared nothing architecture*, **infinite scaling**
 
-### Differences
+### Differentiators
 
 Wasmer Edge and Cloudflare Workers differ in significant ways:
 
+- Wasmer Edge has dedicated private networking for every workload
 - Wasmer Edge **supports multithreaded applications**, while "multi-threading and shared memory are not permitted in [Cloudflare] Workers"
 - Wasmer Edge **can run Python, Rust**, and other languages without any JS glue code, while Cloudflare Workers can only run WebAssembly through JavaScript.
   Example: Django can't run in Cloudflare workers.
-- Wasmer Edge **doesn't require code changes in your application** to run, while you need to adapt your JS code to use the custom Workers SDK to run.
-- Wasmer Edge **can allow any incoming TCP connection**, while Cloudflare Workers can only serve HTTP and websocket requests.
+- Cloudflare workers currently have more PoP's (Points of Presence)