Serverless

When to Use

• Event-driven background tasks (Image processing, Cron jobs).
• APIs with spiky or unpredictable traffic (Auto-scales instantly).
• Startup/MVP where "Scale to Zero" (Zero cost when idle) is critical.
• Glue code between cloud services (e.g., S3 trigger -> Lambda -> DynamoDB).

Quick Start

// AWS Lambda Handler (Node.js)
export const handler = async (event) => {
  console.log("Event received:", JSON.stringify(event));

  const name = event.queryStringParameters?.name || "World";

  return {
    statusCode: 200,
    body: JSON.stringify({ message: `Hello, ${name}!` }),
  };
};

# serverless.yml (Serverless Framework)
service: my-api
provider:
  name: aws
  runtime: nodejs20.x

functions:
  hello:
    handler: handler.hello
    events:
      - httpApi:
          path: /hello
          method: get

Core Concepts

FaaS (Function as a Service)

Cold Start

Statelessness

Common Patterns

Fan-out

Strangler Fig

Best Practices

• Use Frameworks (SST, Serverless Framework, SAM) for IaC.
• optimize Cold Starts (keep functions small, use provisioned concurrency if needed).
• Use Managed Services (DynamoDB, EventBridge) instead of custom code logic.

• Don't use Serverless for Long-Running tasks (Gateways timeout at ~30s, Lambdas at 15m). Use Fargate/Batch for that.
• Don't ignore vendor lock-in (though often the speed creates enough value to justify it).

Troubleshooting

Timeout

OOM (Out of Memory)

References

• Serverless Land (AWS)
• SST (Serverless Stack)