Serverless deployment

[wassfila]

current tests with Astro

Companies

• https://en.m.wikipedia.org/wiki/Vercel
• https://en.m.wikipedia.org/wiki/Netlify
• https://en.m.wikipedia.org/wiki/Cloudflare

Offers

• https://www.netlify.com/pricing/
• https://www.cloudflare.com/plans/application-services/
• https://vercel.com/pricing

aws

• https://aws.amazon.com/lambda/
• Amplify SSR only supports next.js

Docs

• https://vercel.com/docs
• https://docs.netlify.com/
  • endpoint reference https://open-api.netlify.com/
• https://developers.cloudflare.com/
  • https://developers.cloudflare.com/workers/

Support

• https://answers.netlify.com/
• https://vercel.com/help#issues (community based discord)
• https://dash.cloudflare.com/?to=/:account/support
  • Cloudflare Developer Discord

Serverless functions

• netlify
  • functions
  • edge-functions : deno
• vercel
  • serverless
  • edge
  • static
  • middleware.js : comes on top when present on root folder
• cloudflare
  • modes: advanced (workers.js), directory (functions)

Runtime isolation

Not relevant for build time.

• deno node compat : https://github.com/denoland/deno_std/tree/main/node#deno-nodejs-compatibility
• deno deploy does not support dynamic import (can do manual import)
• cloudflare workers runtime does not support 'global'

All

• No fs access
• env read only
• env write with api

List

• netlify : files read n-api
• vercel
• cloudflare
• denoland : deno

Free Tier deploy from Github

• netlify : ok
• cloudflare : ok
• vercel :
  • github organization repo needs Pro
  • No monorepo support (one project per repo)
• aws amplify (monorepo subdirectory error as no .gitmodules found)

Infrastructure

• Vercel (aws, cloudflare)
• Netlify (backend : aws, cdn : cloudflare ???)
• cloudflare (aws)

Other

• vercel, netlify : members of the MACH Alliance https://en.m.wikipedia.org/wiki/MACH_Alliance
• server based (not serverless) https://aws.amazon.com/lightsail/pricing/