aws-serverless

Topics in the source

• AWS Serverless
• Patterns
• Lambda Handler Pattern
• API Gateway Integration Pattern
• Event-Driven SQS Pattern
• Anti-Patterns
• ❌ Monolithic Lambda
• ❌ Large Dependencies

Proper Lambda function structure with error handling When to use: ['Any Lambda function implementation', 'API handlers, event processors, scheduled tasks'] REST API and HTTP API integration with Lambda When to use: ['Building REST APIs backed by Lambda', 'Need HTTP endpoints for functions'] Lambda triggered by SQS for reliable async processing When to use: ['Decoupled, asynchronous processing', 'Need retry logic and DLQ', 'Processing messages in batches'] Why bad: Large deployment packages cause slow cold starts. Hard to scale individual operations. Updates affect entire system. Why bad: Increases deployment package size. Slows down cold starts significantly. Most of SDK/library may be unused. Why bad: VPC-attached Lambdas have ENI setup overhead. Blocking DNS lookups or connections worsen cold starts. | Issue | Severity | Solution | |-------|----------|----------| | Issue | high | ## Measure your INIT phase | | Issue | high | ## Set appropriate timeout | | Issue | high | ## Increase memory allocation | | Issue | medium | ## Verify VPC configuration | | Issue | medium | ## Tell Lambda not to wait for event loop | | Issue | medium | ## For large file uploads | | Issue | high | ## Us

This is an excerpt. Refer to the complete source and its current requirements.