TCP #129: The scoring framework that picks ECS, EKS, or Lambda.

A weighted decision matrix across team maturity, operations, compliance, cost, and ownership with worked examples.

Most AWS compute decisions are made in a conference room. Two engineers argue for their preferred option. A staff engineer summarizes. The team picks. The decision is filed.

The conversation produces an outcome. It does not produce a defensible record. Six months later, when a similar workload arrives, the next team has the same conversation. There is no organizational memory. There is no consistency across teams. The compute estate fragments.

A scoring framework solves this. The framework does not eliminate judgment. It structures judgment so that the same workload produces the same recommendation regardless of which engineer scores it. It also produces a written record that future teams can reference and that leadership can audit when the cost trajectory deviates from the forecast.

The framework below is the one I would use with a real engineering team. It is calibrated for SaaS workloads, weighted for the dimensions that matter at 18-month horizons, and written at a level of detail that can be applied without further interpretation.

---

Why Most Frameworks Fail

Frameworks fail in three predictable ways.

1. Too many dimensions. The team scores 12 attributes. The scoring takes three hours. The team abandons the framework after the second use because it feels like overhead.

2. Wrong dimensions. The framework scores attributes that do not predict success. Language support, AWS region availability, and console UX. These attributes feel important, but rarely change the recommendation.

3. No threshold rules. The framework produces a score for each option, but no rule for what the score means. Three options score within 10 percent of each other. The team argues again. The framework produced no decision support.

The framework below is calibrated against these failure modes. Five dimensions, weighted by 18-month impact, with explicit threshold rules that produce a recommendation rather than a debate.