Editing AWS Lambda (section)

== Understanding (Comprehension) ==
📖 At this level, an expert can **describe**, **summarize**, and **compare** AWS Lambda concepts and behaviors.

* '''Conceptual relationships & contrasts'''
** AWS Lambda vs. '''[https://en.wikipedia.org/wiki/Cloud_computing cloud VMs]''' – No servers to manage or provision.
** Serverless vs. '''[https://en.wikipedia.org/wiki/Microservices microservices]''' – Lambda can implement microservice patterns but is not required.
** AWS Lambda vs. '''[https://en.wikipedia.org/wiki/Containerization containerization]''' – Lambda abstracts runtime environments and scaling.

* '''Core principles & paradigms'''
** Stateless execution — functions do not retain memory between invocations.
** Automatic scaling — concurrency increases as events increase.
** Pay-per-use — costs align with actual execution time.
** Event-driven architecture — workloads react to triggers.

* '''How AWS Lambda works'''
** Code + runtime + configuration = deployed function.
** Execution environments are created on demand.
** Events trigger invocation; outputs return to the calling service.

* '''Producer vs. consumer perspectives'''
** Developer – Writes and packages function logic.
** Platform engineer – Secures, monitors, and manages scaling.
** Application user – Interacts indirectly through APIs, apps, or event triggers.

* '''Typical comprehension-level abilities'''
** Can explain why Lambda is useful.
** Can identify services that can trigger a Lambda function.
** Can describe cold starts and their impact.

----