Part 7 · 1 chapters · ~8 min
Serverless and Edge Deploys
Function versions and aliases with weighted traffic (Lambda), Cloud Run and Cloud Functions revisions, edge deploys on CDNs and Workers, global propagation and its blast radius, cold start effects of deploys, and the frontend specifics from the Infra course.
8
Versions, aliases and global propagation
code
# AWS Lambda: publish a version, shift 10% of the alias to it, watch alarms, then promote
aws lambda publish-version --function-name ledger-webhook # → version 42
aws lambda update-alias --function-name ledger-webhook --name live \
--function-version 41 --routing-config 'AdditionalVersionWeights={"42"=0.1}'
# CodeDeploy can automate: Canary10Percent5Minutes, Linear10PercentEvery1Minute, with CloudWatch alarm rollback| concern | serverless and edge specifics |
|---|---|
| blast radius | an edge deploy reaches every region in seconds; use staged rollouts where the platform offers them, and flags |
| cold starts | a new version starts cold everywhere; traffic shifting warms it gradually |
| state | functions are stateless; migrations and schema compatibility rules still apply |
| frontends | immutable assets and atomic manifest switches, version skew handling (Infra part 7) |