)
中文版 GitHub: https://github.com/geekchow/aws-lambda-guideWhere you are:the entry point of the guide pack.After this file you will know:the whole territory at a glance, how the pack is organized, and which file to read next.This pack explains AWS (Amazon Web Services) Lambda from first principles — why it exists, how a single invocation actually travels through the service, and howversions,aliases, andprovisioned concurrencyfit into that picture. It follows one path:Why → What → Concept map → Running example → Depth dives → Full walkthrough, all held together by a single running example: thecheckoutfunction of an online shop,ShopFast, during Black Friday week.Abbreviation glossaryAbbreviationFull nameMeaning in this guideAWSAmazon Web ServicesAmazon’s cloud platformAPIApplication Programming Interfacee.g. the LambdaInvokeAPI, the Runtime APIARNAmazon Resource Nameglobally unique identifier of an AWS resourcePCProvisioned Concurrencypre-initialized Lambda execution environmentsRCReserved Concurrencya per-function concurrency floor ceilingVMVirtual Machineisolated guest operating systemmicroVMmicro Virtual Machineminimal, fast-booting VM (Firecracker)KVMKernel-based Virtual MachineLinux kernel hypervisor that Firecracker usesAZAvailability Zoneisolated>The whole territory in one picture (mandatory mindmap)Question it answers: what are all the moving parts of Lambda, and how do they group?AWS LambdaProblem it solvesIdle servers cost moneyCapacity planning is guessworkPatching and scaling toilRisky in-place deploysCore conceptsFunctionExecution environmentInvocation and concurrencyVersion immutable snapshotAlias movable pointerProvisioned concurrencyDerived: cold startDerived: reserved concurrencyKey playersVersion storeowns immutable snapshotsAlias routerowns qualifier to versionPC manager plus Auto Scalingowns warm pool sizeInvoke Frontend plus Countingowns admission and limitsAssignment plus Placementowns env routing and creationExecution environmentowns running your codeRunning exampleShopFast checkout on Black Fridaydeploy v8 by canary on alias prodPC 400 warm before 09:00 saleKey flowsWarm invoke happy pathCold start spilloverThrottle 429 at the capCanary rollback by alias flipConnection limits hit before capacityHow the pack is organized01 Why02 What03 Concept map04 Running example05.1 Versions05.2 Aliases05.3 Provisionedconcurrency05.4 Invoke Frontendand Counting05.5 Assignmentand Placement05.6 Executionenvironment05.7 Connection-boundbackends06 Walkthrough07 Next stepsCaption: the reading order — breadth first (01–04), then one dive per key player in the order they appear in the example (05.1–05.6) plus one on connection-bound backends (05.7), then the full replay (06).#FileStageWhat you get0101 WhyWhyThe pain of servers, capacity planning, and in-place deploys0202 WhatWhatOne-sentence definition, boundaries, ecosystem position0303 Concept mapConcept map6 core concepts, 6 key players, coordination diagram0404 Running exampleRunning exampleShopFastcheckoutthrough Black Friday week, traced shallowly05.105.1 VersionsDepthImmutable snapshots,$LATEST, qualified ARNs05.205.2 AliasesDepthPointers, weighted routing, canary rollback05.305.3 Provisioned concurrencyDepthWarm pools, spillover, Auto Scaling, cost05.405.4 Invoke Frontend and concurrencyDepthAdmission, concurrency math, reserved concurrency, throttling05.505.5 Assignment and PlacementDepthFinding a warm environment or creating a new one05.605.6 Execution environmentDepthFirecracker microVM, Init/Invoke/Shutdown, freeze/thaw05.705.7 Connection-bound backendsDepthWhy CloudHSM/database connections run out first; RDS Proxy, KMS key store, service tier0606 WalkthroughWalkthroughThe example end to end at full depth0707 Self-test and labsPracticeExercises, a hands-on lab script, further readingSupporting diagram source: diagrams/lambda-architecture.drawio — the full control-plane >
中文版 GitHub: https://github.com/geekchow/aws-lambda-guideWhere you are:the entry point of the guide pack.After this file you will know:the whole territory at a glance, how the pack is organized, and which file to read next.This pack explains AWS (Amazon Web Services) Lambda from first principles — why it exists, how a single invocation actually travels through the service, and howversions,aliases, andprovisioned concurrencyfit into that picture. It follows one path:Why → What → Concept map → Running example → Depth dives → Full walkthrough, all held together by a single running example: thecheckoutfunction of an online shop,ShopFast, during Black Friday week.Abbreviation glossaryAbbreviationFull nameMeaning in this guideAWSAmazon Web ServicesAmazon’s cloud platformAPIApplication Programming Interfacee.g. the LambdaInvokeAPI, the Runtime APIARNAmazon Resource Nameglobally unique identifier of an AWS resourcePCProvisioned Concurrencypre-initialized Lambda execution environmentsRCReserved Concurrencya per-function concurrency floor ceilingVMVirtual Machineisolated guest operating systemmicroVMmicro Virtual Machineminimal, fast-booting VM (Firecracker)KVMKernel-based Virtual MachineLinux kernel hypervisor that Firecracker usesAZAvailability Zoneisolated>The whole territory in one picture (mandatory mindmap)Question it answers: what are all the moving parts of Lambda, and how do they group?AWS LambdaProblem it solvesIdle servers cost moneyCapacity planning is guessworkPatching and scaling toilRisky in-place deploysCore conceptsFunctionExecution environmentInvocation and concurrencyVersion immutable snapshotAlias movable pointerProvisioned concurrencyDerived: cold startDerived: reserved concurrencyKey playersVersion storeowns immutable snapshotsAlias routerowns qualifier to versionPC manager plus Auto Scalingowns warm pool sizeInvoke Frontend plus Countingowns admission and limitsAssignment plus Placementowns env routing and creationExecution environmentowns running your codeRunning exampleShopFast checkout on Black Fridaydeploy v8 by canary on alias prodPC 400 warm before 09:00 saleKey flowsWarm invoke happy pathCold start spilloverThrottle 429 at the capCanary rollback by alias flipConnection limits hit before capacityHow the pack is organized01 Why02 What03 Concept map04 Running example05.1 Versions05.2 Aliases05.3 Provisionedconcurrency05.4 Invoke Frontendand Counting05.5 Assignmentand Placement05.6 Executionenvironment05.7 Connection-boundbackends06 Walkthrough07 Next stepsCaption: the reading order — breadth first (01–04), then one dive per key player in the order they appear in the example (05.1–05.6) plus one on connection-bound backends (05.7), then the full replay (06).#FileStageWhat you get0101 WhyWhyThe pain of servers, capacity planning, and in-place deploys0202 WhatWhatOne-sentence definition, boundaries, ecosystem position0303 Concept mapConcept map6 core concepts, 6 key players, coordination diagram0404 Running exampleRunning exampleShopFastcheckoutthrough Black Friday week, traced shallowly05.105.1 VersionsDepthImmutable snapshots,$LATEST, qualified ARNs05.205.2 AliasesDepthPointers, weighted routing, canary rollback05.305.3 Provisioned concurrencyDepthWarm pools, spillover, Auto Scaling, cost05.405.4 Invoke Frontend and concurrencyDepthAdmission, concurrency math, reserved concurrency, throttling05.505.5 Assignment and PlacementDepthFinding a warm environment or creating a new one05.605.6 Execution environmentDepthFirecracker microVM, Init/Invoke/Shutdown, freeze/thaw05.705.7 Connection-bound backendsDepthWhy CloudHSM/database connections run out first; RDS Proxy, KMS key store, service tier0606 WalkthroughWalkthroughThe example end to end at full depth0707 Self-test and labsPracticeExercises, a hands-on lab script, further readingSupporting diagram source: diagrams/lambda-architecture.drawio — the full control-plane >
平方复杂度无法被常规优化消除｜TaoToken 统一 Key 通道实测)
