Editing AWS Lambda (section)

== Analyzing (Break Down / Analysis) ==
🔬 At this level, an expert can **examine**, **compare**, and **diagnose** AWS Lambda behavior and architecture.

* '''Comparative analysis'''
** Lambda vs. EC2 — operational burden vs. flexibility.
** Lambda vs. ECS/EKS — ephemeral execution vs. container orchestration.
** Lambda vs. Cloud Functions / Azure Functions — cross-provider trade-offs.

* '''Failure modes & root causes'''
** Timeout due to slow dependencies or networking.
** Throttling caused by insufficient concurrency limits.
** Permissions failures from incorrect IAM roles.

* '''Troubleshooting & observability techniques'''
** Use CloudWatch Logs for debugging errors.
** Inspect distributed traces with AWS X-Ray.
** Monitor concurrency, durations, and error rates.

* '''Architectural insights'''
** Event fan-out through SNS, SQS, or EventBridge.
** Managing shared dependencies using Lambda layers.

* '''Typical analysis-level abilities'''
** Can identify performance bottlenecks.
** Can map system behavior across multiple event sources.
** Can choose between compute options based on workload.

----