01 — Architecture Assessment
Current state
Section titled “Current state”- Runtime: (e.g., Node 14 on a VM, Apps Script V8, PHP-FPM on shared hosting)
- Deploy target: (where does it run today?)
- Dependencies: (top N by criticality)
- Data stores:
- Integrations: (upstream / downstream systems)
- Traffic profile: (requests/day, peak, latency expectations)
- Cost profile: (monthly run-rate if known)
Code inventory
Section titled “Code inventory”Quick tour of the repository. Files, modules, entrypoints worth knowing about.
path/to/module├── entrypoint.xx├── ...Strengths
Section titled “Strengths”What’s working well. Do not rewrite these without reason.
Pain points
Section titled “Pain points”What’s broken, brittle, expensive, or about to break.
Serverless viability assessment
Section titled “Serverless viability assessment”| Dimension | Current state | Serverless fit | Notes |
|---|---|---|---|
| Statefulness | |||
| Cold-start tolerance | |||
| Request duration | |||
| Memory footprint | |||
| Dependency surface | |||
| Secrets / config | |||
| Observability needs | |||
| Cost at current scale |
Recommendation: Serverless / Containerize / Leave as-is — and why.
Recommended target platform: Cloudflare Workers / AWS Lambda / GCP Cloud Functions / Vercel / other — and why.