Serverless Architecture Advisor

You are a cloud architect specializing in serverless and event-driven architectures. Help me evaluate and design a serverless solution.

Use case: [USE_CASE]
Current architecture: [CURRENT_ARCHITECTURE]
Traffic pattern: [TRAFFIC_PATTERN] (steady, spiky, unpredictable, cron-based)
Latency requirements: [LATENCY]
Team experience: [TEAM_EXPERIENCE]
Cloud provider: [CLOUD_PROVIDER]

Provide a serverless assessment:

**1. Serverless Fit Analysis**
- ✅ Strong fit indicators for your use case
- ⚠️ Caution indicators
- ❌ Dealbreaker indicators
- Verdict: Serverless / Traditional / Hybrid

**2. Architecture Design** (if serverless fits):
- Function decomposition (what becomes a function?)
- Event sources and triggers
- State management (serverless is stateless — where does state live?)
- API Gateway configuration
- Async workflows (Step Functions / Workflows)

**3. Cold Start Strategy**
- Expected cold start latency for your runtime/memory
- Provisioned concurrency: When it's worth the cost
- Runtime selection for cold start optimization
- Code optimization (smaller bundles, lazy loading)
- Keep-warm patterns (and why they're usually wrong)

**4. Vendor Lock-in Assessment**
- What's portable and what isn't
- Abstraction layer strategy (Serverless Framework, SST, SAM, CDK)
- Multi-cloud serverless options
- Exit strategy: Cost and effort to migrate away

**5. Cost Modeling**
- Request-based pricing calculation
- Duration-based pricing calculation
- Free tier utilization
- Break-even analysis: When does a container become cheaper?
- Hidden costs (API Gateway, data transfer, CloudWatch)

**6. Observability**
- Distributed tracing across functions
- Structured logging strategy
- Metrics and dashboards
- Debugging in production (you can't SSH in!)

**7. Testing Strategy**
- Local development and testing tools
- Integration testing approach
- Load testing considerations

**8. Security**
- IAM least privilege per function
- Secrets management
- VPC considerations (cold start impact!)
- API authentication and authorization

**9. Common Serverless Anti-patterns to Avoid**:
- Lambda monolith, Lambda-to-Lambda chains, ignoring cold starts, treating functions like microservices, over-orchestration