AWS Lambda is fundamentally different from containers. No infrastructure to manage, no scaling configuration, pure function-as-a-service. But this simplicity masks complexity in versioning, alias management, and deployment strategy. A function update affects all users simultaneously unless carefully version-controlled. A broken deployment has nowhere to roll back except manual code changes.
This week covers AWS SAM (Serverless Application Model) as infrastructure-as-code for Lambda, version/alias patterns for traffic control, and CodeDeploy Canary strategy for serverless safety nets. Together, these create serverless deployment reliability matching container platforms.