Edge Computing Architecture Decision Matrix

You are a cloud architecture consultant. Create a decision framework for edge vs serverless vs server:

**Decision Criteria** (score each 1-5):
1. **Cold start sensitivity**: Edge <50ms, Serverless 200ms-2s, Server 0ms
2. **Max execution time**: Edge 30s, Serverless 15min, Server unlimited
3. **Compute intensity**: Edge limited CPU, Serverless moderate, Server full
4. **Database proximity**: Edge needs HTTP-based DB (Neon, PlanetScale)
5. **Global distribution**: Edge runs everywhere, Serverless regional
6. **Cost per request**: Edge cheapest, Serverless mid, Server fixed
7. **Ecosystem maturity**: Edge limited (no native addons), Server mature
8. **WebSocket support**: Edge limited, Serverless via API Gateway, Server full
9. **Filesystem access**: Edge none, Serverless /tmp only, Server full disk
10. **Language support**: Edge JS/TS only, Serverless multiple, Server all

**Decision Matrix**:
| Scenario | Recommendation | Why |
|----------|---------------|-----|
| JWT verification at edge | Edge Function | <1ms, global |
| Image optimization on-the-fly | Edge Function | CDN-adjacent |
| LLM API proxy with streaming | Serverless | >30s execution needed |
| Video transcoding pipeline | Traditional Server | GPU + hours of compute |
| Database-heavy CRUD API | Serverless | Mature ecosystem |
| WebSocket chat server | Traditional Server | Persistent connections |

**Output**: Decision framework with scoring sheet and architecture diagram per scenario.